Triple
T12799096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matilda II infantry tank |
E305966
|
entity |
| Predicate | mainArmamentCaliber |
P6076
|
FINISHED |
| Object | 40 mm |
—
|
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: 40 mm | Statement: [Matilda II infantry tank, mainArmamentCaliber, 40 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainArmamentCaliber Context triple: [Matilda II infantry tank, mainArmamentCaliber, 40 mm]
-
A.
gunCalibre
chosen
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
B.
primaryArmament
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
-
C.
armamentCapacity
Indicates the maximum quantity or type of weapons or munitions that something is designed or allowed to carry.
-
D.
lightArmament
Indicates that an entity is equipped with or characterized by relatively minimal or lightweight weaponry compared to standard or heavy armament.
-
E.
ammunitionType
Indicates the specific kind or category of ammunition associated with or used by an 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6f858c8190915ede38e9a6a2df |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.