Triple
T8271474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waverley Route |
E193437
|
entity |
| Predicate | partialReopeningDate |
P82431
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Waverley Route, partialReopeningDate, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partialReopeningDate Context triple: [Waverley Route, partialReopeningDate, 2015]
-
A.
reopeningDate
Indicates the date on which something that was previously closed is opened again for use or access.
-
B.
reopeningToPublic
Indicates that an entity, previously closed or restricted, is being opened again for access or use by the general public.
-
C.
reopeningAs
Indicates that an entity that was previously closed or inactive is starting operations again under a new or updated form, identity, or function.
-
D.
relocationOpeningDate
Indicates the date on which a relocation (such as a move or transfer to a new place) is officially opened or becomes effective.
-
E.
softOpeningDate
Indicates the date on which a business, venue, or service begins limited or trial operations before its official grand opening.
- 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7986f8cc8190a529dda980dd6e98 |
completed | March 31, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:50 p.m.