Triple
T14821052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney to Dubbo XPT service |
E348450
|
entity |
| Predicate | classOfTravel |
P35839
|
FINISHED |
| Object | economy class |
—
|
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: economy class | Statement: [Sydney to Dubbo XPT service, classOfTravel, economy class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classOfTravel Context triple: [Sydney to Dubbo XPT service, classOfTravel, economy class]
-
A.
offersClassOfTravel
chosen
Indicates that a service provider makes a particular class or tier of travel (e.g., economy, business, first) available as an option.
-
B.
voyageType
Indicates the specific category or nature of a journey or trip that an entity undertakes.
-
C.
coTraveler
Indicates that two or more entities are traveling together along (part of) the same journey or route.
-
D.
travelClassRelevance
Indicates the degree to which a particular travel class (e.g., economy, business) is pertinent or applicable within a given travel context or scenario.
-
E.
travelsOn
Indicates that an entity moves or journeys using a particular route, path, or mode of transportation.
- 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_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. |
Created at: April 10, 2026, 1:50 a.m.