Triple
T22040742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polet Airlines |
E544630
|
entity |
| Predicate | operatedAntonovAn124 |
P125702
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Polet Airlines, operatedAntonovAn124, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedAntonovAn124 Context triple: [Polet Airlines, operatedAntonovAn124, yes]
-
A.
aircraftRoleOperated
Indicates that an entity operates or has operated in a specified role or function within the context of aircraft operations.
-
B.
aircraftUsedByRussia
Indicates that the aircraft is operated, deployed, or otherwise utilized by Russia.
-
C.
aircraftTypesOperated
chosen
Indicates the types or models of aircraft that an entity (such as an airline or operator) uses or operates.
-
D.
operatesAircraftBrand
Indicates that an entity actively uses or runs aircraft belonging to a specified brand in its operations.
-
E.
operatorOfReferencedAircraft
Indicates that one entity serves as the operator (e.g., managing or controlling party) of an aircraft that is referenced elsewhere in the context.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12828fc788190a22c0e9c2372656b |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:25 p.m.