Triple
T28309231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .300 AAC Blackout |
E713950
|
entity |
| Predicate | requiresChangeFrom5.56 |
P191682
|
FINISHED |
| Object | barrel only |
—
|
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: barrel only | Statement: [.300 AAC Blackout, requiresChangeFrom5.56, barrel only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresChangeFrom5.56 Context triple: [.300 AAC Blackout, requiresChangeFrom5.56, barrel only]
-
A.
requiresUpdate
Indicates that an entity must be refreshed, modified, or brought to a newer state before it can be considered current or valid.
-
B.
changesRequirement
Indicates that one entity modifies, updates, or alters the requirements associated with another entity.
-
C.
modificationRequires
Indicates that performing a modification on one entity is contingent upon satisfying a prerequisite condition or dependency involving another entity.
-
D.
futureChangeRequires
Indicates that a planned or upcoming modification is contingent upon, or must be preceded by, another specified condition, action, or change.
-
E.
upgradeFor
Indicates that one entity serves as an improved or enhanced replacement for another entity.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: April 27, 2026, 11:39 p.m.