Triple
T3899400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ouigo |
E90447
|
entity |
| Predicate | hasLuggagePolicy |
P38285
|
FINISHED |
| Object | restricted included luggage |
—
|
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: restricted included luggage | Statement: [Ouigo, hasLuggagePolicy, restricted included luggage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLuggagePolicy Context triple: [Ouigo, hasLuggagePolicy, restricted included luggage]
-
A.
baggagePolicyType
chosen
Indicates the specific category or type of baggage policy that applies in a given travel or transportation context.
-
B.
baggagePolicySetBy
Indicates that a specific baggage policy is determined, defined, or controlled by a particular entity (such as an airline or service provider).
-
C.
hasBaggageCheck
Indicates that an entity provides or is associated with a service or facility for checking in baggage.
-
D.
hasBaggageService
Indicates that an entity provides or supports services related to handling, storing, or managing baggage for others.
-
E.
hasBaggageClaim
Indicates that a location, typically a transportation hub, includes or provides a baggage claim area for retrieving luggage.
- 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.