Triple
T17859535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northfields tube station |
E446029
|
entity |
| Predicate | rebuildOpeningDate |
P13795
|
FINISHED |
| Object | 1932-01-19 |
—
|
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: 1932-01-19 | Statement: [Northfields tube station, rebuildOpeningDate, 1932-01-19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebuildOpeningDate Context triple: [Northfields tube station, rebuildOpeningDate, 1932-01-19]
-
A.
rerAOpeningDate
Indicates the date on which something (such as a facility, service, or route) is opened again after having been closed.
-
B.
rebuiltOn
Indicates that one entity has been reconstructed, restored, or built again on, over, or using the foundation, structure, or basis of another entity.
-
C.
relocationOpeningDate
Indicates the date on which a relocation (such as a move or transfer to a new place) is officially opened or becomes effective.
-
D.
hasRebuiltDate
chosen
Indicates the date on which something was rebuilt or reconstructed.
-
E.
reerectionDate
Indicates the date on which something that was previously removed, dismantled, or taken down is erected or put back up again.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4978f34948190a25deb4fd617ad72 |
completed | April 19, 2026, 8:51 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.