Triple
T8721821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAMAS F1 |
E207028
|
entity |
| Predicate | grenadeLaunchingCapability |
P6074
|
FINISHED |
| Object | 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: rifle grenades | Statement: [FAMAS F1, grenadeLaunchingCapability, rifle grenades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grenadeLaunchingCapability Context triple: [FAMAS F1, grenadeLaunchingCapability, rifle grenades]
-
A.
grenadeLauncherCompatibility
Indicates that one entity can be equipped with, mounted to, or used in conjunction with a particular grenade launcher.
-
B.
hasSmokeGrenadeLaunchers
Indicates that an entity is equipped with or possesses smoke grenade launching devices.
-
C.
explosiveDevice
Indicates the presence or involvement of an object designed to explode or cause an explosion in relation to the associated entities.
-
D.
ammunitionType
chosen
Indicates the specific kind or category of ammunition associated with or used by an entity.
-
E.
armamentCapacity
Indicates the maximum quantity or type of weapons or munitions that something is designed or allowed to carry.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d03f0848190a50c77e5cd028ee7 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.