Triple
T13135374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magach 3 |
E312067
|
entity |
| Predicate | hasGunStabilization |
P6077
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Magach 3, hasGunStabilization, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGunStabilization Context triple: [Magach 3, hasGunStabilization, yes]
-
A.
gunStabilisation
chosen
Indicates that an entity performs or provides stabilization for a gun, reducing its movement or recoil to improve accuracy.
-
B.
typeOfGunMount
Indicates the specific kind or configuration of gun mounting used to support or attach a gun.
-
C.
weaponControl
Indicates that one entity has authority over, access to, or the ability to direct the use of a weapon associated with another entity.
-
D.
hasArrestingGear
Indicates that an entity is equipped with a system or mechanism used to rapidly decelerate and stop another entity, typically during landing or capture.
-
E.
hasMuzzle
Indicates that one entity possesses or is equipped with a muzzle, typically as a restraining or protective device.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b53fbc8190a0f209c32a00f6cb |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d9804543cc8190a23cd7da59a12a7b |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:08 p.m.