Triple
T32032190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishak |
E817995
|
entity |
| Predicate | airForceOperatorContext |
P94679
|
FINISHED |
| Object | Soviet 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: Soviet Air Force | Statement: [Ishak, airForceOperatorContext, Soviet Air Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airForceOperatorContext Context triple: [Ishak, airForceOperatorContext, Soviet Air Force]
-
A.
airBaseOperator
Indicates that one entity operates, manages, or is responsible for running an air base used for aviation activities.
-
B.
airForceUser
chosen
Indicates that an entity is a member of, affiliated with, or acting on behalf of an air force organization.
-
C.
missionOperator
Indicates that one entity is responsible for operating, managing, or controlling a mission involving another entity.
-
D.
airCommander
Indicates that an entity serves as the commanding officer or leader of air forces or air operations for another entity.
-
E.
airRefuelingOperator
Indicates that one entity performs or is responsible for conducting aerial refueling operations for another entity.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4960b948190ab62e0b5f8bd5537 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:18 a.m.