Triple
T280844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Class (Delta Air Lines) |
E5349
|
entity |
| Predicate | checkInBenefit |
P2188
|
FINISHED |
| Object | priority check‑in (on many routes) |
—
|
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: priority check‑in (on many routes) | Statement: [First Class (Delta Air Lines), checkInBenefit, priority check‑in (on many routes)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checkInBenefit Context triple: [First Class (Delta Air Lines), checkInBenefit, priority check‑in (on many routes)]
-
A.
hasBenefit
chosen
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
B.
supportsBonus
Indicates that one entity provides or enables an additional benefit, reward, or bonus for another entity.
-
C.
checkedBy
Indicates that an entity has been examined, verified, or reviewed by another entity.
-
D.
benefits
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
-
E.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e0868708190ad551ca06cc57f4a |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b765f488190b2cbe4b45cd42821 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.