Triple
T17446197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newtown railway station |
E424789
|
entity |
| Predicate | formerStationBuildingDate |
P75024
|
FINISHED |
| Object | 1878 |
—
|
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: 1878 | Statement: [Newtown railway station, formerStationBuildingDate, 1878]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerStationBuildingDate Context triple: [Newtown railway station, formerStationBuildingDate, 1878]
-
A.
associatedBuildingDate
chosen
Indicates the date on which a particular building is formally linked or related to another entity or record.
-
B.
predecessorBuildingDate
Indicates that one building’s construction date precedes that of another building in a temporal sequence.
-
C.
formerStationOnSiteOpened
Indicates that a former station located on the same site was opened at a specified time.
-
D.
formerStationCode
Indicates that an entity previously had a specific station code that is no longer in current use.
-
E.
formerStationNameFor
Indicates that one station name was previously used as the official name for another station.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ffafec48190b25980318cea353f |
completed | April 19, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.