Triple
T16664792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maesteg Line |
E404952
|
entity |
| Predicate | reopenedForPassengers |
P69628
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [Maesteg Line, reopenedForPassengers, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedForPassengers Context triple: [Maesteg Line, reopenedForPassengers, late 20th century]
-
A.
closedForPassengers
Indicates that a transportation facility or vehicle is not available for use by passengers.
-
B.
reopenedStation
Indicates that a station which was previously closed has been opened again for use or service.
-
C.
openedToPassengerTraffic
Indicates that a transportation facility or route began operating and accepting passengers for regular use.
-
D.
reopenedToTraffic
chosen
Indicates that a previously closed route or transportation facility has been opened again for use by traffic.
-
E.
reopenedFor
Indicates that an entity, previously closed or inactive, has been opened again to allow access, use, or operation for another entity or purpose.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9be0688190afda306cde934c68 |
completed | April 18, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.