Triple
T31071214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kubinka |
E791821
|
entity |
| Predicate | hasAirBaseOperator |
P94363
|
FINISHED |
| Object | Russian Air Force |
—
|
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: Russian Air Force | Statement: [Kubinka, hasAirBaseOperator, Russian Air Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAirBaseOperator Context triple: [Kubinka, hasAirBaseOperator, Russian Air Force]
-
A.
airBaseOperator
chosen
Indicates that one entity operates, manages, or is responsible for running an air base used for aviation activities.
-
B.
hasAirBaseFunction
Indicates that something serves the role or performs the functions of an air base, such as supporting aircraft operations, maintenance, or related activities.
-
C.
isAirBase
Indicates that the subject entity functions as a military air base, i.e., a facility used for operating, housing, and supporting aircraft and related activities.
-
D.
usesAirbaseType
Indicates that one entity makes use of, operates from, or is otherwise functionally associated with a particular type or category of airbase.
-
E.
usesAirbase
Indicates that one entity operates from, accesses, or conducts activities at a particular airbase.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695b566388190a0e6018bf397aa67 |
completed | May 3, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:01 p.m.