Triple
T26035513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oneworld Emerald |
E647539
|
entity |
| Predicate | priorityRank |
P100597
|
FINISHED |
| Object | higher than Oneworld Ruby |
—
|
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: higher than Oneworld Ruby | Statement: [Oneworld Emerald, priorityRank, higher than Oneworld Ruby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: priorityRank Context triple: [Oneworld Emerald, priorityRank, higher than Oneworld Ruby]
-
A.
priorityRule
Indicates that one entity is given precedence or higher processing order over another according to a defined rule or policy.
-
B.
priorityGroup
chosen
Indicates that one entity is assigned to, or associated with, a particular level or category of priority relative to others.
-
C.
priorityDeterminedBy
Indicates that the priority or importance level of one entity is established based on another entity or set of factors.
-
D.
peakRanking
Indicates the highest position or rank an entity has ever achieved within a specified ranking system or context.
-
E.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6061d145c8190bd51d69f0cdabd07 |
completed | May 2, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 9:07 a.m.