Triple
T31989495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | vz. 58 rifle |
E816824
|
entity |
| Predicate | hasFiringModes |
P9011
|
FINISHED |
| Object | semi-automatic |
—
|
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: semi-automatic | Statement: [vz. 58 rifle, hasFiringModes, semi-automatic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFiringModes Context triple: [vz. 58 rifle, hasFiringModes, semi-automatic]
-
A.
fireModes
chosen
Indicates the different ways or settings in which a weapon or device can be fired or operated.
-
B.
hasFiringRange
Indicates that one entity possesses or provides a designated area or capability for discharging weapons over a specified distance.
-
C.
hasFireOnTheMoveCapability
Indicates that an entity is capable of continuing to move while simultaneously delivering effective fire or engaging targets.
-
D.
hasFireControlSystem
Indicates that an entity is equipped with or includes a fire control system used to detect, track, and direct weapons or suppression against targets.
-
E.
firingControl
Indicates a relationship where one entity directs, regulates, or initiates the firing or discharge action of another entity or system.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:13 a.m.