Triple
T8967200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mornington Crescent tube station |
E214167
|
entity |
| Predicate | temporarilyClosedFrom |
P85990
|
FINISHED |
| Object | 1992-10-23 |
—
|
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: 1992-10-23 | Statement: [Mornington Crescent tube station, temporarilyClosedFrom, 1992-10-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporarilyClosedFrom Context triple: [Mornington Crescent tube station, temporarilyClosedFrom, 1992-10-23]
-
A.
reopeningDate
Indicates the date on which something that was previously closed is opened again for use or access.
-
B.
closedFor
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
C.
restaurantClosureDate
Indicates the date on which a restaurant ceases or ceased operations, marking its official closure.
-
D.
partialReopeningDate
Indicates the date on which an entity is reopened in a limited or partial capacity, rather than fully resuming normal operation.
-
E.
closingTime
Indicates the specific time at which a place, service, or activity stops operating or becomes unavailable.
- 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_69ca839cd6008190a1546a701a56710c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc676389948190aa78fdf6a5ae74a5 |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5fcf24348190b6b845205161c0ee |
completed | March 31, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:01 p.m.