Triple
T9150352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AK5 assault rifle |
E219568
|
entity |
| Predicate | isShoulderFired |
P31643
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [AK5 assault rifle, isShoulderFired, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isShoulderFired Context triple: [AK5 assault rifle, isShoulderFired, true]
-
A.
shoulderFired
chosen
Indicates that a weapon is designed to be aimed and discharged from the operator’s shoulder.
-
B.
designedToFire
Indicates that one entity is intended or configured to discharge, launch, or emit another entity (such as a projectile, signal, or event).
-
C.
hasShoulderButtons
Indicates that an object, typically a device or controller, includes buttons positioned on its shoulders or top side edges.
-
D.
isSelectiveFire
Indicates that a firearm is capable of operating in multiple firing modes (such as semi-automatic and fully automatic) selectable by the user.
-
E.
isHeld
Indicates that one entity is physically supported, grasped, or kept in possession by another entity.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca96b57888190a09a563f1fa522f6 |
completed | April 1, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.