Triple
T3129927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.I. Joe: Retaliation |
E65383
|
entity |
| Predicate | usesWeaponry |
P9724
|
FINISHED |
| Object | high-tech military weapons |
—
|
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: high-tech military weapons | Statement: [G.I. Joe: Retaliation, usesWeaponry, high-tech military weapons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesWeaponry Context triple: [G.I. Joe: Retaliation, usesWeaponry, high-tech military weapons]
-
A.
usedWeapon
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
-
B.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
C.
supportsWeapon
Indicates that one entity is capable of accommodating, using, or being compatible with a specified weapon.
-
D.
weaponUsedAgainst
Indicates that a particular weapon or instrument is employed in an act of aggression, attack, or harm directed toward a specific target or entity.
-
E.
involvesWeaponType
chosen
Indicates that the relationship or action includes the use, presence, or association of a specific type or category of weapon.
- 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_69ad8580c72481909672d37acf647893 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada549aaa881908dcf92d20fa6f238 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.