Triple
T7462372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-List |
E176281
|
entity |
| Predicate | boardingGroupAdvantage |
P57572
|
FINISHED |
| Object | earlier access to open seating |
—
|
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: earlier access to open seating | Statement: [A-List, boardingGroupAdvantage, earlier access to open seating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardingGroupAdvantage Context triple: [A-List, boardingGroupAdvantage, earlier access to open seating]
-
A.
boardingGroups
Indicates that certain entities are assigned to or associated with specific boarding groups for an ordered boarding process.
-
B.
boarding
Indicates that one entity is getting onto or entering a vehicle, vessel, or similar conveyance associated with another entity.
-
C.
boardingProcess
Indicates the process or sequence of actions by which passengers move from a waiting area onto a vehicle (such as an airplane, train, or bus).
-
D.
boardingOffered
Indicates that the provision of boarding or lodging services is being made available to one or more entities.
-
E.
boardingPolicy
chosen
Indicates the rules or procedures governing how and in what order passengers are allowed to board a vehicle or vessel.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d80ae08190ba383066cf0cb2ce |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:39 p.m.