Triple
T3899389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ouigo |
E90447
|
entity |
| Predicate | serviceClassStructure |
P44501
|
FINISHED |
| Object | single-class seating |
—
|
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: single-class seating | Statement: [Ouigo, serviceClassStructure, single-class seating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceClassStructure Context triple: [Ouigo, serviceClassStructure, single-class seating]
-
A.
serviceClass
Indicates the classification or category of service associated with or provided by an entity in the relationship.
-
B.
hasServiceStructure
chosen
Indicates that one entity provides, contains, or is associated with a particular service-related structure or organizational framework for delivering a service.
-
C.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
-
D.
programStructure
Indicates how components, modules, or elements are organized and related within a program or system.
-
E.
serviceComponent
Indicates that one entity functions as a component or sub-part within the structure or implementation of a larger service.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.