Triple
T28047795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Madison Street |
E708728
|
entity |
| Predicate | hasCurrentLandmark |
P43158
|
FINISHED |
| Object | United Center |
—
|
NE NERFINISHED |
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: United Center | Statement: [West Madison Street, hasCurrentLandmark, United Center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentLandmark Context triple: [West Madison Street, hasCurrentLandmark, United Center]
-
A.
hasLandmarkStatusIn
Indicates that an entity holds a recognized landmark status within a specified geographic or administrative area.
-
B.
hasFormerNearbyLandmark
Indicates that an entity previously had a nearby landmark that no longer exists or no longer holds the same status or relevance.
-
C.
isLocalLandmark
Indicates that something is recognized as a notable or significant landmark within a specific local area or community.
-
D.
hasLandmarkProperty
Indicates that something possesses a notable or defining landmark-related characteristic or feature.
-
E.
isLandmarkFor
chosen
Indicates that one entity serves as a notable or significant reference point or attraction for another entity, such as a place, route, or area.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 27, 2026, 8:30 p.m.