Triple
T31915293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFGSC |
E814809
|
entity |
| Predicate | overseesWeaponSystem |
P180555
|
FINISHED |
| Object | B-52 Stratofortress |
—
|
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: B-52 Stratofortress | Statement: [AFGSC, overseesWeaponSystem, B-52 Stratofortress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesWeaponSystem Context triple: [AFGSC, overseesWeaponSystem, B-52 Stratofortress]
-
A.
weaponSystemAssociatedWith
Indicates that one entity is functionally or organizationally connected to a particular weapon system, such as by using, supporting, or being part of that system.
-
B.
weaponSystemType
Indicates the specific category or kind of weapon system associated with an entity.
-
C.
opposingWeaponSystem
Indicates that one weapon system is designed, used, or configured to counter, neutralize, or operate in direct opposition to another weapon system.
-
D.
usedOnWeaponSystem
Indicates that something (such as a component, technology, or material) is employed as part of, or in conjunction with, a weapon system.
-
E.
hasFireControlSystem
Indicates that an entity is equipped with or includes a fire control system used to detect, track, and direct weapons or suppression against targets.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: May 1, 2026, 12:02 a.m.