Triple
T30014958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boxer RCH 155 |
E762569
|
entity |
| Predicate | caliberStandard |
P47473
|
FINISHED |
| Object | NATO 155 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: NATO 155 mm | Statement: [Boxer RCH 155, caliberStandard, NATO 155 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caliberStandard Context triple: [Boxer RCH 155, caliberStandard, NATO 155 mm]
-
A.
gunCalibre
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
B.
standardCaliberOfCountry
Indicates that a particular caliber is officially recognized or commonly used as the standard caliber within a given country.
-
C.
supportsCaliber
Indicates that one entity is compatible with and able to accommodate or function with a specified caliber.
-
D.
standardUSNATOCaliber
chosen
Indicates that an item’s caliber conforms to the standard ammunition dimensions used by U.S. and NATO military forces.
-
E.
standardBulletWeight
Indicates the typical or commonly accepted mass of a given type of bullet under standard specifications.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f679838da08190a06048a2b5f60f70 |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:45 p.m.