Triple
T19977345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westbury, Houston |
E493725
|
entity |
| Predicate | hasBuildingAge |
P32323
|
FINISHED |
| Object | many homes built in the 1950s and 1960s |
—
|
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: many homes built in the 1950s and 1960s | Statement: [Westbury, Houston, hasBuildingAge, many homes built in the 1950s and 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingAge Context triple: [Westbury, Houston, hasBuildingAge, many homes built in the 1950s and 1960s]
-
A.
hasHousingStockAge
chosen
Indicates the relationship between an entity and the age or period of construction of its available housing stock.
-
B.
hasBuildingPeriod
Indicates that a building or structure is associated with a specific time period during which it was constructed or significantly developed.
-
C.
associatedBuildingDate
Indicates the date on which a particular building is formally linked or related to another entity or record.
-
D.
hasBuildingStatus
Indicates the current condition, classification, or operational state assigned to a building.
-
E.
hasBuildingGrade
Indicates that a building is assigned a particular grade or quality rating.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d1054e08190993b92b86ec5bbc8 |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:27 p.m.