Triple
T2038154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volgograd International Airport |
E44679
|
entity |
| Predicate | isOperatedAs |
P4445
|
FINISHED |
| Object | civilian airport |
—
|
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: civilian airport | Statement: [Volgograd International Airport, isOperatedAs, civilian airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOperatedAs Context triple: [Volgograd International Airport, isOperatedAs, civilian airport]
-
A.
operatedAs
chosen
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
B.
formerOperates
Indicates that an entity previously operated or managed another entity but no longer does so.
-
C.
operatedWith
Indicates that an entity performed an action, function, or process using a specified tool, method, or instrument.
-
D.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
E.
operatedThrough
Indicates that an action, process, or influence is carried out or mediated via a particular intermediary, channel, or mechanism.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb95062c481908058d6da35337680 |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.