Triple
T28219566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RPK light machine gun |
E711413
|
entity |
| Predicate | gasBlockFeature |
P164136
|
FINISHED |
| Object | lacks gas cutoff for launching rifle grenades |
—
|
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: lacks gas cutoff for launching rifle grenades | Statement: [RPK light machine gun, gasBlockFeature, lacks gas cutoff for launching rifle grenades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gasBlockFeature Context triple: [RPK light machine gun, gasBlockFeature, lacks gas cutoff for launching rifle grenades]
-
A.
gasReleased
Indicates that a gas is emitted or discharged from a source into its surrounding environment.
-
B.
hasBlock
Indicates that one entity possesses, contains, or is associated with a specific block or blocking element in relation to another entity.
-
C.
canBlock
Indicates that one entity has the ability or permission to prevent, obstruct, or stop the action or effect of another entity.
-
D.
block
Indicates preventing or obstructing another entity’s action, movement, or access.
-
E.
activationBlock
Indicates that one entity prevents or inhibits the activation or functioning of another entity.
- 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6434f9f888190bd43fde92cd729fe |
completed | May 2, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 10:45 p.m.