Triple
T6929028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afghan Air Force |
E160385
|
entity |
| Predicate | usesAirbaseType |
P73720
|
FINISHED |
| Object | military airbase |
—
|
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: military airbase | Statement: [Afghan Air Force, usesAirbaseType, military airbase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAirbaseType Context triple: [Afghan Air Force, usesAirbaseType, military airbase]
-
A.
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.
-
B.
hasReuseOfAirBase
Indicates that one entity makes use of an air base that is originally owned, operated, or primarily used by another entity.
-
C.
hasAirfieldType
Indicates that an airfield is classified as having a particular type or category of airfield.
-
D.
usesCarrierAircraft
Indicates that one entity employs or operates aircraft that are designed to be launched from and recovered by an aircraft carrier.
-
E.
usedByAirForce
Indicates that something is employed, operated, or otherwise utilized by an air force.
- F. None of above. chosen
Provenance (4 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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6da1de28881908579bc198e74203e |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bb577c81908ee8b415b4281f3d |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d98625c88190a37fdf6d95d7fcbd |
completed | March 27, 2026, 7:24 p.m. |
Created at: March 27, 2026, 2:27 p.m.