Triple
T15537171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Shell |
E370376
|
entity |
| Predicate | offensiveUse |
P33725
|
FINISHED |
| Object | launched forward |
—
|
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: launched forward | Statement: [Green Shell, offensiveUse, launched forward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offensiveUse Context triple: [Green Shell, offensiveUse, launched forward]
-
A.
offensiveStrategy
Indicates a strategic approach focused on attacking or aggressively advancing against an opponent.
-
B.
offensiveCharacteristic
Indicates that one entity possesses a trait, behavior, or quality that is considered insulting, disrespectful, or likely to cause offense to another entity or group.
-
C.
usedOffensiveSystem
chosen
Indicates that an entity employed an offensive system (such as a weapon or attack mechanism) against another entity or target.
-
D.
offense
Indicates that one entity commits, causes, or is responsible for a violation, wrongdoing, or rule-breaking act against another entity or governing norms.
-
E.
offensiveOperation
Indicates an action or campaign in which a party actively initiates hostile or military measures against an opponent.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442f3c688190a599165e526af2ed |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.