Triple
T28438374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MG5 |
E715634
|
entity |
| Predicate | intendedCaliberStandard |
P172928
|
FINISHED |
| Object | NATO |
—
|
NE NERFINISHED |
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 | Statement: [MG5, intendedCaliberStandard, NATO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedCaliberStandard Context triple: [MG5, intendedCaliberStandard, NATO]
-
A.
isLargerCaliberCounterpartOf
Indicates that one item is the higher-caliber version or counterpart of another, typically within the same general type or family of objects.
-
B.
gunCalibre
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
C.
standardChambering
Indicates that an entity uses a conventional or commonly accepted method of arranging or configuring its internal chambers or compartments.
-
D.
caliberClass
chosen
Indicates a classification relationship where an entity is assigned to a specific caliber category based on its size or measurement.
-
E.
rangeStandardAmmunition
Indicates that the relationship specifies the standard type of ammunition used for a given range or weapon system.
- 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 28, 2026, 1:44 a.m.