Triple
T20023142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D-Zug |
E494910
|
entity |
| Predicate | hadSubtypes |
P138402
|
FINISHED |
| Object | night D-Zug services |
—
|
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: night D-Zug services | Statement: [D-Zug, hadSubtypes, night D-Zug services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSubtypes Context triple: [D-Zug, hadSubtypes, night D-Zug services]
-
A.
hasTypeOfSubdivision
Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
-
B.
hasSubunits
Indicates that an entity is composed of or organized into smaller constituent units that are part of its structure.
-
C.
hasSubrole
Indicates that one role functions as a more specific, subordinate, or specialized version of another broader role.
-
D.
hasSubConcept
Indicates that one concept is a more specific, subordinate, or narrower idea within the scope of another, more general concept.
-
E.
hasMultipleSubclasses
Indicates that a class or category is related to more than one distinct subclass within a hierarchy.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6628a1ecc8190bf6ee0bedb61e0b8 |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:35 p.m.