Triple
T36161850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 62d Operations Group |
E1045898
|
entity |
| Predicate | typeOfAirlift |
P178676
|
FINISHED |
| Object | strategic airlift |
—
|
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: strategic airlift | Statement: [62d Operations Group, typeOfAirlift, strategic airlift]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAirlift Context triple: [62d Operations Group, typeOfAirlift, strategic airlift]
-
A.
airliftType
chosen
Indicates the specific method or category of air transport used to move people or goods, such as emergency, military, or logistical airlift.
-
B.
airliftedExternallyBy
Indicates that an entity is transported through the air by an external carrier or mechanism, rather than by its own power.
-
C.
airliftOrganizedBy
Indicates that an airlift operation is planned, coordinated, or managed by a specified organizing entity.
-
D.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
-
E.
aircraftTypesCarried
Indicates that one entity (typically a vessel, facility, or platform) carries or is capable of carrying specific types of aircraft as part of its operations or configuration.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a023f290e3081909a465d6cfb79518a |
completed | May 11, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_6a0238d1436c8190ab0251030b01902e |
completed | May 11, 2026, 8:15 p.m. |
Created at: May 3, 2026, 4:08 p.m.