Triple
T38046945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 185th Air Refueling Wing |
E949643
|
entity |
| Predicate | secondaryCapability |
P200253
|
FINISHED |
| Object | airlift support |
—
|
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: airlift support | Statement: [185th Air Refueling Wing, secondaryCapability, airlift support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryCapability Context triple: [185th Air Refueling Wing, secondaryCapability, airlift support]
-
A.
secondaryAbility
chosen
Indicates that an entity possesses an additional, supporting, or less primary capability or power beyond its main ability.
-
B.
primaryCapability
Indicates that one entity serves as the main or most important functional ability, role, or competence of another entity.
-
C.
associatedCapability
Indicates that one entity has a related ability, function, or competence that is linked to or relevant for another entity.
-
D.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
E.
consideredCapability
Indicates that something is regarded or evaluated as a potential capability of an 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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffc516d1908190b475f5a6156b0ca8 |
completed | May 9, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69ffc4a946e08190b3535a5dc15ac484 |
completed | May 9, 2026, 11:35 p.m. |
Created at: May 3, 2026, 4:20 p.m.