Triple
T11384756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haruka limited express |
E269686
|
entity |
| Predicate | primaryPassengerGroup |
P99024
|
FINISHED |
| Object | air travelers |
—
|
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: air travelers | Statement: [Haruka limited express, primaryPassengerGroup, air travelers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPassengerGroup Context triple: [Haruka limited express, primaryPassengerGroup, air travelers]
-
A.
passengers
Indicates that one entity is traveling in or being transported by another entity, typically as a non-operating occupant.
-
B.
hasPassengerRole
Indicates that an entity participates in a context or event specifically in the capacity or role of a passenger.
-
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.
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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:34 p.m.