Triple
T16353769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RPG-7 |
E397119
|
entity |
| Predicate | backblast |
P123090
|
FINISHED |
| Object | significant backblast zone behind operator |
—
|
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: significant backblast zone behind operator | Statement: [RPG-7, backblast, significant backblast zone behind operator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backblast Context triple: [RPG-7, backblast, significant backblast zone behind operator]
-
A.
backsUp
Indicates that one entity provides support, reinforcement, or confirmation for another entity’s actions, statements, or position.
-
B.
backDescription
Indicates that an entity provides a description or textual information specifically about the back side or rear view of another entity.
-
C.
backing
Indicates providing support, endorsement, or financial/resources assistance to someone or something, often enabling or strengthening their actions or position.
-
D.
backType
Indicates the type or category of a backing or support associated with an entity.
-
E.
laterBlownUpTo
Indicates that one entity is subsequently destroyed or blown up at a later time relative to another referenced event or state.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2facd80dc8190b08f0eecbf787240 |
completed | April 18, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:07 a.m.