Triple
T25168000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim Preston |
E630234
|
entity |
| Predicate | passengerStatus |
P138095
|
FINISHED |
| Object | paying passenger |
—
|
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: paying passenger | Statement: [Jim Preston, passengerStatus, paying passenger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerStatus Context triple: [Jim Preston, passengerStatus, paying passenger]
-
A.
airlineStatus
Indicates the current operational or membership state of an airline, such as its activity, certification, or alliance standing.
-
B.
IATAStatus
Indicates the current operational or membership status of an entity with respect to the International Air Transport Association (IATA).
-
C.
fareStatus
Indicates the current condition or classification of a fare within a pricing or ticketing context (e.g., available, restricted, or expired).
-
D.
aircraftStatus
Indicates the current operational condition or state of an aircraft (e.g., active, grounded, in maintenance, or decommissioned).
-
E.
currentPassengerRole
chosen
Indicates the specific role or capacity an individual currently holds as a passenger in a given context or trip.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46d43e6d08190bbd8643ea058ceea |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:18 p.m.