Triple
T27344068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blazer |
E684182
|
entity |
| Predicate | ammunitionCategory |
P6074
|
FINISHED |
| Object | centerfire rifle cartridges |
—
|
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: centerfire rifle cartridges | Statement: [Blazer, ammunitionCategory, centerfire rifle cartridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ammunitionCategory Context triple: [Blazer, ammunitionCategory, centerfire rifle cartridges]
-
A.
ammunitionType
chosen
Indicates the specific kind or category of ammunition associated with or used by an entity.
-
B.
ammunitionCapacity
Indicates the maximum amount of ammunition that something (typically a weapon or container) is designed to hold at one time.
-
C.
munitionWeightCategory
Indicates the classification of a munition based on its weight range or weight-related category.
-
D.
lightArmament
Indicates that an entity is equipped with or characterized by relatively minimal or lightweight weaponry compared to standard or heavy armament.
-
E.
weaponCategory
Indicates the classification or type of weapon to which an item or armament belongs.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62ba0fedc8190b63a546f7d893676 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 11:44 a.m.