Triple
T15831182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyon bus network |
E383874
|
entity |
| Predicate | primaryTicketType |
P28113
|
FINISHED |
| Object | TCL single ticket |
—
|
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: TCL single ticket | Statement: [Lyon bus network, primaryTicketType, TCL single ticket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTicketType Context triple: [Lyon bus network, primaryTicketType, TCL single ticket]
-
A.
primaryTicketingSystem
Indicates that one ticketing system is designated as the main or default system used for handling tickets in a given context.
-
B.
primaryType
chosen
Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
-
C.
ticketTypeExample
Indicates that an entity serves as an example or illustrative instance of a particular ticket type.
-
D.
primaryUserType
Indicates the main or dominant category of user associated with an entity or interaction.
-
E.
ticketTypeStored
Indicates that a particular type of ticket has been recorded and saved in a storage or system.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e6433ac8190a3d3e0d573673ea3 |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.