Triple
T20023283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IR |
E494913
|
entity |
| Predicate | primaryPassengerSegment |
P99024
|
FINISHED |
| Object | inter-regional 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: inter-regional travellers | Statement: [IR, primaryPassengerSegment, inter-regional travellers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPassengerSegment Context triple: [IR, primaryPassengerSegment, inter-regional travellers]
-
A.
primaryPassengerGroup
chosen
Indicates the main group of passengers that is most directly associated with or served by a given entity or context.
-
B.
secondaryPassengerProfile
Indicates that an entity serves as an additional or non-primary passenger associated with a main travel booking or passenger profile.
-
C.
passengerSegments
Indicates a relationship where a journey or trip is divided into distinct legs or segments that a passenger travels through.
-
D.
majorPassengerService
Indicates that a transportation facility or route provides primary or significant passenger service as one of its main functions.
-
E.
primaryPassengerOperatorOnRoute
Indicates that an operator is the main provider of passenger services on a specific route.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6628a1ecc8190bf6ee0bedb61e0b8 |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:35 p.m.