Triple
T9881915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GoggleWorks Center for the Arts |
E180827
|
entity |
| Predicate | buildingConversionType |
P42263
|
FINISHED |
| Object | adaptive reuse |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: adaptive reuse | Statement: [GoggleWorks Center for the Arts, buildingConversionType, adaptive reuse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingConversionType Context triple: [GoggleWorks Center for the Arts, buildingConversionType, adaptive reuse]
-
A.
buildingConvertedTo
Indicates that one building has been transformed, repurposed, or adapted into another type or use of building.
-
B.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
C.
buildingReuseType
chosen
Indicates the manner or purpose for which an existing building is reused or repurposed.
-
D.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
E.
originalBuildingType
Indicates the type or category of building that something was initially constructed or designated to be, before any later changes or repurposing.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca828082cc8190a40f8d299caa6545 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb418417c8190b00dea8916a2e102 |
completed | April 2, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:38 p.m.