Triple
T3231913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Fe Building (Chicago) |
E67758
|
entity |
| Predicate | hasCityDesignation |
P974
|
FINISHED |
| Object | Chicago Landmark |
—
|
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 Landmark | Statement: [Santa Fe Building (Chicago), hasCityDesignation, Chicago Landmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityDesignation Context triple: [Santa Fe Building (Chicago), hasCityDesignation, Chicago Landmark]
-
A.
hasCityDesignatedAs
Indicates that an entity has a specific city formally assigned or designated to it in a particular role or capacity.
-
B.
cityPlanningDesignation
Indicates how an area is officially classified or designated within urban or municipal planning (e.g., residential, commercial, industrial).
-
C.
hasDesignation
chosen
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
D.
hasCriticalDesignation
Indicates that an entity has been assigned a status or label marking it as critical in importance, priority, or required attention.
-
E.
mapDesignation
Indicates a formal label or identifier that is assigned to something specifically for use on a map.
- 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_69ad858c61888190a31196310d9b30b5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaed99d2c8190950fa883ec6f1f8e |
completed | March 8, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0dc2248190a38c40f4e06cd41c |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:08 p.m.