Triple
T14821106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney to Moree Xplorer service |
E348451
|
entity |
| Predicate | ticketTypeAccepted |
P115850
|
FINISHED |
| Object | NSW TrainLink paper tickets |
—
|
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: NSW TrainLink paper tickets | Statement: [Sydney to Moree Xplorer service, ticketTypeAccepted, NSW TrainLink paper tickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketTypeAccepted Context triple: [Sydney to Moree Xplorer service, ticketTypeAccepted, NSW TrainLink paper tickets]
-
A.
ticketTypeExample
Indicates that an entity serves as an example or illustrative instance of a particular ticket type.
-
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.
ticketTypeStored
Indicates that a particular type of ticket has been recorded and saved in a storage or system.
-
D.
ticketFormat
Indicates the specific structure, layout, or template in which a ticket is represented or issued.
-
E.
ticketIncludes
Indicates that a particular ticket grants access to, contains, or covers the specified item, service, or component.
- F. None of above. chosen
Provenance (4 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe64328819083ce42704cf0602d |
completed | April 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:50 a.m.