Triple
T3899414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ouigo |
E90447
|
entity |
| Predicate | ticketDistribution |
P49264
|
FINISHED |
| Object | primarily direct-to-consumer |
—
|
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: primarily direct-to-consumer | Statement: [Ouigo, ticketDistribution, primarily direct-to-consumer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketDistribution Context triple: [Ouigo, ticketDistribution, primarily direct-to-consumer]
-
A.
distributionBy
chosen
Indicates how something is allocated, arranged, or spread according to a specified criterion or grouping.
-
B.
distributesIn
Indicates that one entity allocates or hands out something (e.g., items, resources, information) within or across a specified area, group, or context.
-
C.
ticketDemand
Indicates that there is a level of desire or need among potential buyers for tickets to an event, service, or offering.
-
D.
distribution
Indicates the act or pattern of giving, delivering, or spreading something from one source to multiple recipients or locations.
-
E.
ticket
Indicates that an entity serves as or is associated with a ticket, typically representing authorization, access, or a record for an event, service, or transaction.
- 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.