Triple
T25972776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oneworld Ruby |
E645850
|
entity |
| Predicate | validAcross |
P2335
|
FINISHED |
| Object | Oneworld member airlines |
—
|
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: Oneworld member airlines | Statement: [Oneworld Ruby, validAcross, Oneworld member airlines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: validAcross Context triple: [Oneworld Ruby, validAcross, Oneworld member airlines]
-
A.
across
Indicates a spatial relationship where one entity is on the opposite side of, or extending from one side to the other side of, another entity or area.
-
B.
appliesAcross
chosen
Indicates that a condition, rule, or property holds uniformly over multiple items, cases, or contexts.
-
C.
allowsTravelAcross
Indicates that one entity enables or permits movement or passage from one side or location to another across a separating space or boundary.
-
D.
hasCross
Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
-
E.
runsAcross
Indicates that one entity moves quickly on foot from one side of another entity, area, or boundary to the opposite side, traversing it in a roughly straight path.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605055e68819098ab1a9d803ce6a3 |
completed | May 2, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 8:51 a.m.