Triple
T6122600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AeroCaribbean Flight 883 |
E136518
|
entity |
| Predicate | onboardNationalities |
P68260
|
FINISHED |
| Object | Cuban nationals |
—
|
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: Cuban nationals | Statement: [AeroCaribbean Flight 883, onboardNationalities, Cuban nationals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onboardNationalities Context triple: [AeroCaribbean Flight 883, onboardNationalities, Cuban nationals]
-
A.
bearerNationality
Indicates that one entity is the country or nationality associated with the bearer of another entity, such as a document or credential.
-
B.
definedCitizenship
Indicates that a formal citizenship status has been legally established or specified for an entity.
-
C.
nationalityInWorld
Indicates that an entity has a specific national affiliation or citizenship within the world context.
-
D.
operatorNationality
Indicates that an operator has a specific national affiliation or country of origin.
-
E.
nationalityLawOf
Indicates that one entity is the body of law or legal framework that defines or governs the nationality or citizenship status associated with another entity.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05c247b7081909972b40afb165e6f |
completed | March 22, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:14 p.m.