Triple
T4143865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glessner House |
E89335
|
entity |
| Predicate | cityRegionContext |
P32691
|
FINISHED |
| Object | Chicago’s Gilded Age elite neighborhood |
—
|
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: Chicago’s Gilded Age elite neighborhood | Statement: [Glessner House, cityRegionContext, Chicago’s Gilded Age elite neighborhood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityRegionContext Context triple: [Glessner House, cityRegionContext, Chicago’s Gilded Age elite neighborhood]
-
A.
regionOfCity
Indicates that a specified area or district is a constituent part or subdivision of a particular city.
-
B.
homeCityRegion
Indicates the city or broader regional area that serves as an entity’s primary place of residence or origin.
-
C.
regionContext
chosen
Indicates the broader geographic or spatial setting within which an entity, event, or relationship is situated or interpreted.
-
D.
cityServedRegion
Indicates that a city provides services to, or functions as an administrative or economic center for, a specified region.
-
E.
hostCityRegion
Indicates the city or broader region that serves as the host location for a specified event or entity.
- 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.