Triple
T11923318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gresham, Chicago |
E283714
|
entity |
| Predicate | hasHistoricHousingStock |
P32323
|
FINISHED |
| Object | brick bungalows |
—
|
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: brick bungalows | Statement: [Gresham, Chicago, hasHistoricHousingStock, brick bungalows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricHousingStock Context triple: [Gresham, Chicago, hasHistoricHousingStock, brick bungalows]
-
A.
housingTypeHistoric
Indicates that an entity’s housing type is classified based on historical or heritage-related characteristics.
-
B.
hasHousingStockAge
chosen
Indicates the relationship between an entity and the age or period of construction of its available housing stock.
-
C.
residenceHistoric
Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
-
D.
historicallyHoused
Indicates that one entity served as a location or container for another entity at some time in the past.
-
E.
hasNearbyHistoricalEstate
Indicates that one entity is located close to another entity that is a recognized historical estate.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8e2fc648190a446c1917db1c7d9 |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.