Triple
T5313088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arriva |
E119079
|
entity |
| Predicate | hasSubsidiary |
P254
|
FINISHED |
| Object | Arriva Denmark |
E119079
|
NE 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: Arriva Denmark | Statement: [Arriva, hasSubsidiary, Arriva Denmark]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arriva Denmark Context triple: [Arriva, hasSubsidiary, Arriva Denmark]
-
A.
Arriva
chosen
Arriva is a major European public transport company that operates bus, coach, train, tram, and waterbus services across multiple countries.
-
B.
Arriva Czech Republic
Arriva Czech Republic is a public transport operator in the Czech Republic, providing bus and rail services as part of the international Arriva group.
-
C.
Arriva Croatia
Arriva Croatia is a Croatian public transport operator providing regional and intercity bus services as part of the wider European Arriva Group.
-
D.
Metro Service A/S
Metro Service A/S is the company responsible for operating and managing the Copenhagen Metro system in Denmark.
-
E.
Go-Ahead Nordic
Go-Ahead Nordic is a Scandinavian rail operator that runs passenger train services in Norway, including routes serving major hubs like Oslo Central Station.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd446b57bc8190a513d2e6c40314f3 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8536c06c81908ef8ba8c39b4fa30 |
completed | March 20, 2026, 5:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf188988688190b4b08b5e0cda8cf5 |
completed | March 21, 2026, 10:15 p.m. |
Created at: March 20, 2026, 1:54 p.m.