Triple
T5958739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EuroCity |
E132580
|
entity |
| Predicate | hasServiceStandard |
P67069
|
FINISHED |
| Object | minimum comfort and speed criteria |
—
|
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: minimum comfort and speed criteria | Statement: [EuroCity, hasServiceStandard, minimum comfort and speed criteria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceStandard Context triple: [EuroCity, hasServiceStandard, minimum comfort and speed criteria]
-
A.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
B.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
C.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
D.
hasServiceChief
Indicates that one entity serves as the chief or head responsible for overseeing the services of another entity.
-
E.
hasStandardSeries
Indicates that an entity is associated with, or belongs to, a designated standard series or standardized sequence.
- 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_69c0086c2364819091e9fe2f58fa2517 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03fb7f8a88190a8bd45208bda4a03 |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0335a635881909c58c1ef0f97f1e8 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03fb6bb7c81909c5629fba408dc69 |
completed | March 22, 2026, 7:15 p.m. |
Created at: March 22, 2026, 4:02 p.m.