Triple
T22452892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gare d’Orange |
E555036
|
entity |
| Predicate | hasTicketingServices |
P3383
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gare d’Orange, hasTicketingServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketingServices Context triple: [Gare d’Orange, hasTicketingServices, yes]
-
A.
hasTicketing
chosen
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
B.
ticketingCompatibleWith
Indicates that two systems, services, or components can interoperate or be used together within the same ticketing or reservation workflow without conflict.
-
C.
hasTicketingAuthority
Indicates that an entity possesses the official power or permission to issue, manage, or control tickets for an event, service, or system.
-
D.
hasTicketIntegration
Indicates that there is an established connection enabling ticket-related data or actions to be shared or synchronized between systems or components.
-
E.
hasElectronicTicketing
Indicates that an entity supports or provides electronic ticketing for access, booking, or transactions.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4d6368819082cafbbd83339fbf |
completed | April 29, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.