Triple
T5099651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | InterRegio |
E114951
|
entity |
| Predicate | positionInServiceHierarchy |
P5163
|
FINISHED |
| Object | between InterCity and RegionalExpress |
—
|
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: between InterCity and RegionalExpress | Statement: [InterRegio, positionInServiceHierarchy, between InterCity and RegionalExpress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInServiceHierarchy Context triple: [InterRegio, positionInServiceHierarchy, between InterCity and RegionalExpress]
-
A.
positionInHierarchy
chosen
Indicates that one entity occupies a specific rank or level relative to another within an ordered hierarchy.
-
B.
positionInCascade
Indicates the specific step or level an element occupies within an ordered cascade or sequence of dependent stages.
-
C.
positionInNetwork
Indicates the specific role or location an entity occupies within a network’s structure or topology.
-
D.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
-
E.
positionInWork
Indicates the specific role, rank, or placement an entity holds within a larger work or structured composition.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7568e9c881909f114973faef6832 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.