Triple
T14545843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney–Melbourne air route |
E341288
|
entity |
| Predicate | secondaryPassengerProfile |
P114882
|
FINISHED |
| Object | leisure travellers |
—
|
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: leisure travellers | Statement: [Sydney–Melbourne air route, secondaryPassengerProfile, leisure travellers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryPassengerProfile Context triple: [Sydney–Melbourne air route, secondaryPassengerProfile, leisure travellers]
-
A.
primaryPassengerGroup
Indicates the main group of passengers that is most directly associated with or served by a given entity or context.
-
B.
passengerSegments
Indicates a relationship where a journey or trip is divided into distinct legs or segments that a passenger travels through.
-
C.
secondaryCustomer
Indicates a relationship where one customer is designated as an additional or subordinate customer associated with a primary customer in a given context.
-
D.
hasPassengerRole
Indicates that an entity participates in a context or event specifically in the capacity or role of a passenger.
-
E.
formerPassengerService
Indicates that an entity previously provided passenger transportation services but no longer does so.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb1bfc2b48190adb0897682c26a9a |
completed | April 14, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de610330a48190b558235a14c0dc9f |
completed | April 14, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:22 a.m.