Triple
T37620577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lafayette Park neighborhood |
E936055
|
entity |
| Predicate | housingStockAge |
P32323
|
FINISHED |
| Object | older housing stock |
—
|
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: older housing stock | Statement: [Lafayette Park neighborhood, housingStockAge, older housing stock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: housingStockAge Context triple: [Lafayette Park neighborhood, housingStockAge, older housing stock]
-
A.
hasHousingStockAge
chosen
Indicates the relationship between an entity and the age or period of construction of its available housing stock.
-
B.
housePlacementYear
Indicates the year in which a house was placed, built, or established at a given location.
-
C.
yearBuilt
Indicates the specific year in which something (typically a structure or object) was constructed or completed.
-
D.
infrastructureAge
Indicates the length of time that a piece of infrastructure has existed since its construction or installation.
-
E.
housingTypeHistoric
Indicates that an entity’s housing type is classified based on historical or heritage-related characteristics.
- 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.