Triple
T28219558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RPK light machine gun |
E711413
|
entity |
| Predicate | bipod |
P164134
|
FINISHED |
| Object | folding bipod mounted near muzzle |
—
|
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: folding bipod mounted near muzzle | Statement: [RPK light machine gun, bipod, folding bipod mounted near muzzle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bipod Context triple: [RPK light machine gun, bipod, folding bipod mounted near muzzle]
-
A.
heldBenchIn
Indicates that an individual previously held a judicial position on a specified court or bench.
-
B.
bayonetMount
Indicates that one object is equipped with or designed to accept a bayonet-style mounting connection to another object.
-
C.
bearerPosition
Indicates the spatial or positional relationship of a bearer (holder or carrier) relative to the item or entity it bears.
-
D.
beam
Indicates that one entity emits, directs, or projects a concentrated line or stream (such as light, energy, or information) toward another entity.
-
E.
bolting
Indicates that an entity is rapidly and suddenly moving away or fleeing from another entity or location.
- 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.