Triple
T20959954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICE 4 |
E516212
|
entity |
| Predicate | operatorServiceType |
P5884
|
FINISHED |
| Object | long-distance passenger service |
—
|
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: long-distance passenger service | Statement: [ICE 4, operatorServiceType, long-distance passenger service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorServiceType Context triple: [ICE 4, operatorServiceType, long-distance passenger service]
-
A.
typicalOperatorService
Indicates that an entity commonly performs or provides a particular operational service in a standard or expected manner.
-
B.
operatesService
chosen
Indicates that an agent runs, manages, or provides a particular service.
-
C.
operationType
Indicates the specific kind of operation or action being performed or recorded in the relationship between entities.
-
D.
serviceProviderType
Indicates the category or kind of service provider associated with an entity or transaction.
-
E.
operatesUnitType
Indicates that an entity runs, manages, or controls a unit of a specified type.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb6e50988190a564d2aaf1a9bc54 |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 1:30 p.m.