Triple
T35899350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newcourt railway station |
E1038311
|
entity |
| Predicate | hasOperatorAtOpening |
P97989
|
FINISHED |
| Object | First Great Western |
—
|
NE NERFINISHED |
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: First Great Western | Statement: [Newcourt railway station, hasOperatorAtOpening, First Great Western]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOperatorAtOpening Context triple: [Newcourt railway station, hasOperatorAtOpening, First Great Western]
-
A.
lineOpeningOperator
Indicates that an operator is responsible for initiating or opening a line, such as a production line, communication line, or service line.
-
B.
openingOperator
chosen
Indicates that an entity initiates or performs the action of opening another entity or resource.
-
C.
hasOpeningFunction
Indicates that an entity possesses a specific function or role related to opening something (e.g., access, initiation, or activation).
-
D.
hasAdditionalOperator
Indicates that an entity is associated with one or more supplementary operators beyond its primary or default operator.
-
E.
hasOpeningType
Indicates that one entity has, features, or is characterized by a particular type or kind of opening.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 3, 2026, 4:07 p.m.