Triple
T9468491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Airways Concorde Room |
E228332
|
entity |
| Predicate | positionInBrandHierarchy |
P48676
|
FINISHED |
| Object | flagship lounge |
—
|
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: flagship lounge | Statement: [British Airways Concorde Room, positionInBrandHierarchy, flagship lounge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInBrandHierarchy Context triple: [British Airways Concorde Room, positionInBrandHierarchy, flagship lounge]
-
A.
positionInBrandPortfolio
chosen
Indicates the relative role or rank that a brand holds within a company’s overall brand portfolio.
-
B.
positionInProductLine
Indicates the specific place or order an item occupies within a defined product line or series.
-
C.
positionInHierarchy
Indicates that one entity occupies a specific rank or level relative to another within an ordered hierarchy.
-
D.
positionOnFranchise
Indicates the specific role, rank, or status an entity holds within a particular franchise or franchise-based organization.
-
E.
orderHierarchy
Indicates a hierarchical ordering relationship where one entity is positioned above or below another in a structured sequence or chain of command.
- 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_69ca846fee388190a6ec273fd644b88b |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fdf604481909bf7d7d477230ca3 |
completed | April 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:53 p.m.