Triple
T37484760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transport in the East of England |
E931500
|
entity |
| Predicate | majorRailOperator |
P121930
|
FINISHED |
| Object | Greater Anglia |
—
|
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: Greater Anglia | Statement: [Transport in the East of England, majorRailOperator, Greater Anglia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRailOperator Context triple: [Transport in the East of England, majorRailOperator, Greater Anglia]
-
A.
formerRailOperator
Indicates that an entity previously operated a rail service or railway system but no longer does so.
-
B.
hasRailTransportOperator
chosen
Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
-
C.
railwayCompany
Indicates that one entity is a railway company that owns, operates, or manages railway services or infrastructure in relation to another entity.
-
D.
laterRailwayCompany
Indicates that one railway company is the successor or later incarnation of another railway company.
-
E.
railwayCompanyOnRoute
Indicates that a particular railway company operates or provides service on a specified route.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a000014497c819088d5cda3977522dd |
completed | May 10, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69ffff9a52b08190be1024e0fb6fe661 |
completed | May 10, 2026, 3:46 a.m. |
Created at: May 3, 2026, 4:17 p.m.