Triple
T30115983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metrojet Flight 9268 bombing |
E765417
|
entity |
| Predicate | passengerNationalities |
P68260
|
FINISHED |
| Object | mostly Russian |
—
|
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: mostly Russian | Statement: [Metrojet Flight 9268 bombing, passengerNationalities, mostly Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerNationalities Context triple: [Metrojet Flight 9268 bombing, passengerNationalities, mostly Russian]
-
A.
onboardNationalities
chosen
Indicates the set of nationalities present among the people on board a given vehicle, vessel, or craft.
-
B.
commonVisitorNationalities
Indicates that the related entity has visitors whose nationalities are commonly represented among its overall visitor population.
-
C.
bearerNationality
Indicates that one entity is the country or nationality associated with the bearer of another entity, such as a document or credential.
-
D.
nationalityInOutieWorld
Indicates that an entity has a specific nationality within the fictional or defined context of "OutieWorld."
-
E.
visitingNationality
Indicates the nationality of a person or group that is visiting a particular place or host.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 29, 2026, 7:12 p.m.