Triple
T37188938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meon Valley Railway |
E921396
|
entity |
| Predicate | freightClosureDate |
P185344
|
FINISHED |
| Object | 1968-08-30 |
—
|
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: 1968-08-30 | Statement: [Meon Valley Railway, freightClosureDate, 1968-08-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freightClosureDate Context triple: [Meon Valley Railway, freightClosureDate, 1968-08-30]
-
A.
closedOnDate
chosen
Indicates that an entity ceases or ceased operations or availability on a specific calendar date.
-
B.
closureTime
Indicates the time at which an entity, event, or process is formally closed, ended, or no longer available.
-
C.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
-
D.
carriageDate
Indicates the date on which the carriage or transport of goods or passengers is scheduled to occur or actually takes place.
-
E.
permanentClosureAnnouncementDate
Indicates the date on which an official announcement was made that something (such as a facility, service, or location) will be permanently closed.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.