Triple
T5068283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Terrace |
E114196
|
entity |
| Predicate | hasHousingEra |
P32323
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [River Terrace, hasHousingEra, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHousingEra Context triple: [River Terrace, hasHousingEra, mid-20th century]
-
A.
hasHousingStockAge
chosen
Indicates the relationship between an entity and the age or period of construction of its available housing stock.
-
B.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
C.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
D.
historicallyHoused
Indicates that one entity served as a location or container for another entity at some time in the past.
-
E.
urbanDevelopmentEra
Indicates the historical period or phase during which significant urban development or transformation of a place occurred.
- 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd749dd1a08190858fa739df024eb4 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.