Triple
T144665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnificent Mile |
E2927
|
entity |
| Predicate | urbanPlanningEra |
P561
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Magnificent Mile, urbanPlanningEra, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanPlanningEra Context triple: [Magnificent Mile, urbanPlanningEra, 20th century]
-
A.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
B.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
C.
notableEra
chosen
Indicates the historical period or era for which an entity is especially recognized or significant.
-
D.
cityDuringImperialPeriod
Indicates that a location functioned as a city during a specified imperial or empire-dominated historical period.
-
E.
historicalEmpireCenter
Indicates that a location served as the primary political or administrative center of a historical empire.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257e935bc8190a03e54a10e9ba6f7 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a25656a4fc81908a87678ac3d28f93 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.