Triple
T31795415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Transit Authority |
E811581
|
entity |
| Predicate | successorInNewcastleOperations |
P198939
|
FINISHED |
| Object | Keolis Downer Hunter |
—
|
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: Keolis Downer Hunter | Statement: [State Transit Authority, successorInNewcastleOperations, Keolis Downer Hunter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInNewcastleOperations Context triple: [State Transit Authority, successorInNewcastleOperations, Keolis Downer Hunter]
-
A.
successorForce
Indicates that one force or power succeeds, replaces, or takes over the role of another force.
-
B.
successorCampaign
Indicates that one campaign directly follows and continues or replaces another campaign in sequence.
-
C.
successorSystem
Indicates that one system directly follows and replaces another in function, role, or version.
-
D.
successorInUK
Indicates that one entity directly follows another in a succession specific to the United Kingdom, such as in an official role, title, or office.
-
E.
successorEngine
Indicates that one engine directly follows and replaces another in a sequence or version lineage.
- F. None of above. chosen
Provenance (4 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
| PDg | Predicate description generation | batch_69ff167608f08190b7cd2cf65ddecbf3 |
completed | May 9, 2026, 11:11 a.m. |
Created at: April 30, 2026, 11:40 p.m.