Triple
T28217919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Metropolitan Square |
E711368
|
entity |
| Predicate | isRecognizableBuildingIn |
P124480
|
FINISHED |
| Object | St. Louis |
—
|
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: St. Louis | Statement: [One Metropolitan Square, isRecognizableBuildingIn, St. Louis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRecognizableBuildingIn Context triple: [One Metropolitan Square, isRecognizableBuildingIn, St. Louis]
-
A.
isSkyscraperIn
Indicates that a skyscraper is located within or belongs to a specified geographic area or place.
-
B.
emblematicBuildingLocation
Indicates that a building serves as a symbolic or representative landmark for a particular location or area.
-
C.
isDowntownLandmark
Indicates that a location is recognized as a notable or prominent landmark within a city’s downtown area.
-
D.
isUrbanLandmark
chosen
Indicates that a place or structure is recognized as a notable or significant landmark within an urban environment.
-
E.
isLandmarkFor
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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6434ed8cc8190ae45736d0b678275 |
completed | May 2, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 10:44 p.m.