Triple
T33111215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuxhaven station |
E847335
|
entity |
| Predicate | hasPassengerServiceStatus |
P199231
|
FINISHED |
| Object | in operation |
—
|
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: in operation | Statement: [Cuxhaven station, hasPassengerServiceStatus, in operation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPassengerServiceStatus Context triple: [Cuxhaven station, hasPassengerServiceStatus, in operation]
-
A.
hasPassengerServicesType
Indicates the type or category of passenger services that are provided or associated with an entity.
-
B.
hasPassengerServiceLevel
Indicates the level or quality of passenger service provided in a given transportation context.
-
C.
hasPassengerServicesTo
Indicates that a transportation provider operates passenger services connecting one location or entity to another.
-
D.
hasPassengerServiceBrand
Indicates that a passenger transport service operates under or is associated with a specific commercial brand or service name.
-
E.
isInPassengerService
Indicates that an entity (such as a vehicle, vessel, or aircraft) is currently being used to carry passengers as part of regular service.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
| PDg | Predicate description generation | batch_69ff27b0385c8190bccf340d26268f77 |
completed | May 9, 2026, 12:25 p.m. |
Created at: May 1, 2026, 1:27 a.m.