Triple
T448516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Airlines Flagship Lounge |
E7074
|
entity |
| Predicate | differentiation |
P6335
|
FINISHED |
| Object | more premium than Admirals Club |
—
|
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: more premium than Admirals Club | Statement: [American Airlines Flagship Lounge, differentiation, more premium than Admirals Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differentiation Context triple: [American Airlines Flagship Lounge, differentiation, more premium than Admirals Club]
-
A.
distinction
Indicates that one entity is recognized, treated, or classified as different or separate from another.
-
B.
division
Indicates a relationship where one entity is separated or partitioned into parts, groups, or sections based on some criterion or operation.
-
C.
differentiatedFrom
chosen
Indicates that one entity is distinguished or set apart from another by identifying differences between them.
-
D.
hasDerivative
Indicates that one entity is derived, obtained, or produced from another through some transformation, process, or modification.
-
E.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef6755a08190a057e72279b70456 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2ede1a1108190a4a06b3416ae6156 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.