Triple
T5584794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ebbw Valley |
E146727
|
entity |
| Predicate | railwayReopened |
P29809
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Ebbw Valley, railwayReopened, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayReopened Context triple: [Ebbw Valley, railwayReopened, 2008]
-
A.
railwayLineOpened
Indicates that a railway line began official operation or service on a specified date.
-
B.
railwayWorksOpened
chosen
Indicates that a railway facility, such as a station, line, or related infrastructure, was officially opened or began operation on a specified date.
-
C.
railwayOpenedWith
Indicates that a railway line or section was inaugurated and began operation together with a specified associated element (such as a station, segment, or service).
-
D.
railwayWorksClosed
Indicates that a railway workshop, depot, or related railway works facility has ceased operations or been officially closed.
-
E.
formerRailwayLine
Indicates that a railway line previously existed in the past but is no longer in operation or has been decommissioned.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02085d0e48190b8d185fe7f3d8579 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.