Triple
T26122379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunteren |
E659005
|
entity |
| Predicate | operatorOfLocalTrains |
P45263
|
FINISHED |
| Object | Connexxion |
E617839
|
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: Connexxion | Statement: [Lunteren, operatorOfLocalTrains, Connexxion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorOfLocalTrains Context triple: [Lunteren, operatorOfLocalTrains, Connexxion]
-
A.
servesLocalTrains
Indicates that a station or facility provides service or stops specifically for local (non-express) train routes.
-
B.
hasLocalRailOperator
chosen
Indicates that a specified rail operator is responsible for providing local or regional rail services within a particular area or network.
-
C.
hasRegionalTrainService
Indicates that a location or route is served by regional train services connecting it to nearby areas.
-
D.
railServicesTo
Indicates that rail transportation services operate from one location to another specified destination.
-
E.
trainsOn
Indicates that one entity receives training, instruction, or practice using or based on another entity (such as a resource, dataset, tool, or subject).
- F. None of above.
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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a112759ed788190bbf086bf2b1ffef3 |
completed | May 23, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 26, 2026, 8:09 p.m.