Triple
T22040724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rossiya Special Flight Detachment |
E544629
|
entity |
| Predicate | typeOfOperator |
P21524
|
FINISHED |
| Object | non-scheduled operator |
—
|
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: non-scheduled operator | Statement: [Rossiya Special Flight Detachment, typeOfOperator, non-scheduled operator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfOperator Context triple: [Rossiya Special Flight Detachment, typeOfOperator, non-scheduled operator]
-
A.
typeOf
Indicates that one entity is a specific kind, class, or category instance of another more general entity.
-
B.
typeOfValue
Indicates that one entity specifies the kind or category of value associated with another entity.
-
C.
typeOfExpression
Indicates that one entity is classified as a specific kind or category of expression represented by the other entity.
-
D.
typicalOperatorType
chosen
Indicates the usual or most common type or category of operator associated with a given entity or context.
-
E.
typeOfCondition
Indicates that one condition is a specific kind, category, or subtype of another condition.
- 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.