Triple
T30481350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riyadh Air |
E775595
|
entity |
| Predicate | fleetOrder |
P169486
|
FINISHED |
| Object | Boeing 787-9 Dreamliner |
—
|
NE NERFINISHED |
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: Boeing 787-9 Dreamliner | Statement: [Riyadh Air, fleetOrder, Boeing 787-9 Dreamliner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleetOrder Context triple: [Riyadh Air, fleetOrder, Boeing 787-9 Dreamliner]
-
A.
fleetCommander
Indicates that one entity serves as the commanding officer or overall leader in charge of the operations and decisions of a fleet associated with another entity.
-
B.
fleetPosition
Indicates the spatial location or coordinates of a fleet relative to a defined reference frame or area.
-
C.
fleetBase
Indicates that one entity serves as the primary homeport, headquarters, or main operating base for a fleet associated with the other entity.
-
D.
fleetConfiguration
Indicates how multiple vehicles or vessels are organized, arranged, or structured together as a coordinated fleet.
-
E.
militaryOrder
Indicates a formal directive or command issued within a military context from a superior authority to subordinates, requiring compliance.
- 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_69f687415610819081818d08f7c79a81 |
completed | May 2, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 8:12 p.m.