Triple
T37831705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 300 Central Park West |
E943219
|
entity |
| Predicate | hasStartOfConstructionYear |
P4034
|
FINISHED |
| Object | 1929 |
—
|
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: 1929 | Statement: [300 Central Park West, hasStartOfConstructionYear, 1929]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStartOfConstructionYear Context triple: [300 Central Park West, hasStartOfConstructionYear, 1929]
-
A.
hasConstructionEndYear
Indicates the year in which the construction of an entity was completed.
-
B.
constructionStartYear
chosen
Indicates the calendar year in which the construction of something was begun.
-
C.
constructionResumptionYear
Indicates the year in which a previously halted or paused construction activity was resumed.
-
D.
startOfConstructionApprox
Indicates that the construction of something began around an approximate or estimated point in time, rather than on a precisely known date.
-
E.
startsYearOn
Indicates that a specified time period or calendar year begins on a particular date or day.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a009a0e1fa481909ed881012009b268 |
completed | May 10, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_6a0092e9fcb08190a966d720684f25ec |
completed | May 10, 2026, 2:15 p.m. |
Created at: May 3, 2026, 4:19 p.m.