Triple
T28414717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EM-2 rifle |
E719768
|
entity |
| Predicate | reasonForNonAdoption |
P81260
|
FINISHED |
| Object | NATO ammunition standardization issues |
—
|
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 ammunition standardization issues | Statement: [EM-2 rifle, reasonForNonAdoption, NATO ammunition standardization issues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForNonAdoption Context triple: [EM-2 rifle, reasonForNonAdoption, NATO ammunition standardization issues]
-
A.
reasonForNonInstallation
Indicates the explanation or cause for why an expected installation did not occur.
-
B.
reasonForLimitedAdoption
chosen
Indicates the factor or explanation that accounts for why something has not been widely or fully adopted.
-
C.
reasonForNonParticipation
Indicates the explanation or cause for why an entity did not take part in a specified activity or event.
-
D.
reasonForDecline
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
-
E.
reasonForNonRelease
Indicates the specific cause or justification for why something was not released or made available.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 1:29 a.m.