Triple
T5290819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go-Ahead Nordic |
E119735
|
entity |
| Predicate | operatesPassengerServices |
P31751
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Go-Ahead Nordic, operatesPassengerServices, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesPassengerServices Context triple: [Go-Ahead Nordic, operatesPassengerServices, true]
-
A.
operatedPassengerServices
chosen
Indicates that an entity provided and managed transportation services specifically for carrying passengers.
-
B.
hasPassengerServicesTo
Indicates that a transportation provider operates passenger services connecting one location or entity to another.
-
C.
hasPassengerOperations
Indicates that an entity conducts or supports transportation services specifically for carrying passengers.
-
D.
hasPassengerOperator
Indicates that an entity (such as a vehicle or service) is operated by an organization or person responsible for carrying passengers.
-
E.
operatesInterCityServices
Indicates that an entity runs or provides transportation services connecting different cities.
- 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_69bd446de5648190b313a90bd96730d2 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8682d18c8190bbb35cc75c8a7c12 |
completed | March 20, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69bd844dfdac819086efedd1cbebff84 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:52 p.m.