Triple
T13202959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5.56×45mm NATO |
E314285
|
entity |
| Predicate | hasPrimerType |
P109032
|
FINISHED |
| Object | small rifle |
—
|
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: small rifle | Statement: [5.56×45mm NATO, hasPrimerType, small rifle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimerType Context triple: [5.56×45mm NATO, hasPrimerType, small rifle]
-
A.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
B.
isPrimaryTypeAvailable
Indicates whether a primary or main type associated with an entity is currently available or defined.
-
C.
hasPrimitive
Indicates that an entity is composed of, defined by, or associated with one or more basic, indivisible components or elements.
-
D.
hasPrimaryCode
Indicates that an entity is associated with its main or most important identifying code among potentially multiple codes.
-
E.
PRIMOSType
Indicates that an entity is classified according to a specific PRIMOS system type or category.
- F. None of above. chosen
Provenance (4 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98ceeb22c8190a6be666031d9e5a4 |
completed | April 10, 2026, 11:51 p.m. |
Created at: April 9, 2026, 9:16 p.m.