Triple
T36781716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Isotope |
E908785
|
entity |
| Predicate | usedFirearms |
P820
|
FINISHED |
| Object | small arms |
—
|
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: small arms | Statement: [Operation Isotope, usedFirearms, small arms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedFirearms Context triple: [Operation Isotope, usedFirearms, small arms]
-
A.
weaponsUsed
chosen
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
B.
organicWeaponSystems
Indicates a relationship where weapon systems are composed of, derived from, or integrated with living or biological components rather than being purely mechanical or synthetic.
-
C.
weaponUsedOn
Indicates that a particular weapon was employed or applied against a specific target or entity.
-
D.
usesFirearmsUnit
Indicates that one entity employs or operates firearms as part of a specific unit or organizational grouping.
-
E.
weaponOfInterest
Indicates that an entity is a weapon that is specifically relevant, notable, or targeted for attention within a given context or scenario.
- 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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 3, 2026, 4:12 p.m.