Triple
T5099677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | InterRegio |
E114951
|
entity |
| Predicate | fareLevel |
P9546
|
FINISHED |
| Object | usually cheaper than InterCity |
—
|
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: usually cheaper than InterCity | Statement: [InterRegio, fareLevel, usually cheaper than InterCity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareLevel Context triple: [InterRegio, fareLevel, usually cheaper than InterCity]
-
A.
fare
Indicates the price or cost required for a person or thing to be transported by a particular mode of travel or service.
-
B.
fareType
Indicates the category or class of fare (such as standard, discounted, or promotional) that applies to a given trip, ticket, or pricing instance.
-
C.
fareControlUnifiedWith
Indicates that separate fare control areas are combined into a single, shared fare-controlled zone.
-
D.
amenityLevel
chosen
Indicates the degree or quality of facilities, services, or conveniences provided in relation to something.
-
E.
fareBasis
Indicates the specific fare rule or pricing category that applies to a ticket or travel segment.
- 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.