Triple
T32695047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairchild Republic A-10 Thunderbolt II |
E835983
|
entity |
| Predicate | cannonCaliber |
P6076
|
FINISHED |
| Object | 30 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: 30 mm | Statement: [Fairchild Republic A-10 Thunderbolt II, cannonCaliber, 30 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannonCaliber Context triple: [Fairchild Republic A-10 Thunderbolt II, cannonCaliber, 30 mm]
-
A.
gunCalibre
chosen
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
B.
isLargerCaliberCounterpartOf
Indicates that one item is the higher-caliber version or counterpart of another, typically within the same general type or family of objects.
-
C.
hasArtilleryCaliber
Indicates that an artillery piece is characterized by or equipped with a specific caliber (diameter) of its gun barrel or ammunition.
-
D.
natoCaliberClass
Indicates that two ammunition types share the same standardized NATO caliber classification.
-
E.
hasCannon
Indicates that one entity is equipped with, contains, or features a cannon.
- 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:10 a.m.