Triple
T7048904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old East Dallas |
E163714
|
entity |
| Predicate | buildingStockEra |
P32323
|
FINISHED |
| Object | pre-World War II housing |
—
|
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: pre-World War II housing | Statement: [Old East Dallas, buildingStockEra, pre-World War II housing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingStockEra Context triple: [Old East Dallas, buildingStockEra, pre-World War II housing]
-
A.
buildingUsedSince
Indicates that a particular building has been in use starting from a specified point in time.
-
B.
constructionCentury
Indicates the century during which something was constructed or built.
-
C.
urbanDevelopmentEra
Indicates the historical period or phase during which significant urban development or transformation of a place occurred.
-
D.
eraOfMajorConstruction
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
E.
hasHousingStockAge
chosen
Indicates the relationship between an entity and the age or period of construction of its available housing stock.
- 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_69c6885f598c8190b6b6495c59d8d962 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bb602081908bfa6186a1f5a4b4 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:37 p.m.