Triple
T32300718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 307th Bomb Wing |
E825230
|
entity |
| Predicate | gainsTo |
P154730
|
FINISHED |
| Object | Air Force Global Strike Command |
—
|
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: Air Force Global Strike Command | Statement: [307th Bomb Wing, gainsTo, Air Force Global Strike Command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainsTo Context triple: [307th Bomb Wing, gainsTo, Air Force Global Strike Command]
-
A.
gainedBy
Indicates that something comes to possess, obtain, or receive something else as a result of an action, process, or event.
-
B.
gainedFrom
Indicates that something is obtained, acquired, or derived as a result of a specified source or cause.
-
C.
gained
Indicates that one entity has come to possess, acquire, or increase in something (such as an object, quality, or amount) relative to another point or state.
-
D.
gainedStatus
chosen
Indicates that an entity has acquired or achieved a particular status, condition, or role as a result of some event or process.
-
E.
obtains
Indicates that one entity comes into possession or control of another entity, typically through some action or process.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd7481988190addeb1c9acd75386 |
completed | May 3, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:45 a.m.