Triple
T8194850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MetroTech Center |
E191402
|
entity |
| Predicate | planningPeriod |
P48987
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [MetroTech Center, planningPeriod, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningPeriod Context triple: [MetroTech Center, planningPeriod, 1980s]
-
A.
planningYear
Indicates the year in which planning or preparation activities for something are scheduled or designated to occur.
-
B.
zoningPlanPeriod
chosen
Indicates the time span or duration for which a particular zoning plan is valid or in effect.
-
C.
periodProperty
Indicates a temporal characteristic or attribute associated with a specific time period or interval.
-
D.
periodizedAs
Indicates that something has been divided or organized into distinct time periods according to a particular periodization scheme.
-
E.
timePeriodProposed
Indicates that a specific time period has been suggested or put forward for consideration or adoption.
- 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5c20fbd08190b9966e3c967e9c71 |
completed | March 31, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:42 p.m.