Triple
T13135342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magach 3 |
E312067
|
entity |
| Predicate | primaryArmamentModel |
P88584
|
FINISHED |
| Object | 105 mm L7 gun |
—
|
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: 105 mm L7 gun | Statement: [Magach 3, primaryArmamentModel, 105 mm L7 gun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryArmamentModel Context triple: [Magach 3, primaryArmamentModel, 105 mm L7 gun]
-
A.
primaryArmament
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
-
B.
mainGunModel
chosen
Indicates the specific model or type designation of the primary gun or main weapon system used by an entity.
-
C.
primaryArmamentLayout
Indicates how the main weapons or primary armament of an entity are arranged or distributed relative to that entity.
-
D.
primaryArms
Indicates that the subject possesses or uses the specified arms or weapons as its main or most important set.
-
E.
secondaryArmament
Indicates that one entity serves as a secondary or auxiliary weapon system associated with another primary platform or armament.
- 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.