Triple
T29257812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Station (Nashville) |
E741751
|
entity |
| Predicate | isReusedBuilding |
P89097
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Union Station (Nashville), isReusedBuilding, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReusedBuilding Context triple: [Union Station (Nashville), isReusedBuilding, yes]
-
A.
buildingReuseType
Indicates the manner or purpose for which an existing building is reused or repurposed.
-
B.
reusedIn
Indicates that something previously used in one context or instance is used again in another context or instance.
-
C.
reconstructedBuilding
Indicates that a building has been rebuilt or restored after damage, destruction, or significant alteration.
-
D.
buildingReuse
chosen
Indicates that an existing building is being repurposed or adapted for a new use rather than being newly constructed or demolished.
-
E.
hasBuildingFrom
Indicates a relationship where a location or site possesses or includes a building that originates from, or was constructed in, a specified time period, source, or context.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f664af8ca48190bfd74d02b761a1b4 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:39 p.m.