Triple
T19855919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dearborn Station |
E477130
|
entity |
| Predicate | redevelopmentDate |
P137587
|
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: [Dearborn Station, redevelopmentDate, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redevelopmentDate Context triple: [Dearborn Station, redevelopmentDate, 1980s]
-
A.
redevelopmentStartDate
Indicates the date on which a redevelopment project or process officially begins.
-
B.
redevelopmentEnd
Indicates the point in time or event at which a redevelopment process or project is considered completed or ceases.
-
C.
redevelopedAfter
Indicates that one entity was redeveloped at a later time than, and as a subsequent phase or replacement to, another entity.
-
D.
redevelopmentInvolved
Indicates that an entity participated in or was associated with the process of redeveloping another entity, such as land, property, or infrastructure.
-
E.
redevelopmentFor
Indicates a relationship where one entity is intended, designated, or used for the redevelopment of another entity.
- F. None of above. chosen
Provenance (4 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6586c14fc81908d34785f1088b0a9 |
completed | April 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:51 p.m.