Triple
T19888683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compagnie Internationale des Wagons-Lits |
E477970
|
entity |
| Predicate | providedServiceOn |
P55997
|
FINISHED |
| Object | international long-distance trains |
—
|
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: international long-distance trains | Statement: [Compagnie Internationale des Wagons-Lits, providedServiceOn, international long-distance trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedServiceOn Context triple: [Compagnie Internationale des Wagons-Lits, providedServiceOn, international long-distance trains]
-
A.
providesServiceOn
chosen
Indicates that one entity offers or performs a service during, on, or in connection with a specified time, date, or schedule.
-
B.
providesServices
Indicates that one entity supplies or performs services for the benefit or use of another entity.
-
C.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of another entity.
-
D.
offeredService
Indicates that one entity has provided or made available a service to another entity.
-
E.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6590c1b9c8190abbfaa04b80713b3 |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.