Triple
T30481360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riyadh Air |
E775595
|
entity |
| Predicate | marketPositionGoal |
P174731
|
FINISHED |
| Object | major global carrier |
—
|
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: major global carrier | Statement: [Riyadh Air, marketPositionGoal, major global carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketPositionGoal Context triple: [Riyadh Air, marketPositionGoal, major global carrier]
-
A.
marketPosition
Indicates the relative standing or rank an entity holds within a specific market compared to its competitors.
-
B.
targetedPosition
Indicates a relationship where an action, influence, or focus is specifically directed toward a particular position, role, or location.
-
C.
manufacturerGoal
Indicates that a manufacturer has a specific objective, target, or desired outcome it aims to achieve.
-
D.
machineGoal
Indicates that a machine or automated system has a specific objective, target state, or outcome it is intended or programmed to achieve.
-
E.
strategicGoal
Indicates that one entity represents a long-term objective or desired outcome that another entity is intentionally aiming to achieve or align actions toward.
- F. None of above. chosen
Provenance (4 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6c5b7e46081909975b05f7298cc0e |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c49069e48190a3486b6254a6645b |
completed | May 3, 2026, 3:44 a.m. |
Created at: April 29, 2026, 8:12 p.m.