Triple
T28309288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 6.5 Grendel |
E713951
|
entity |
| Predicate | advantageOver 7.62×39mm |
P164674
|
FINISHED |
| Object | flatter trajectory |
—
|
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: flatter trajectory | Statement: [6.5 Grendel, advantageOver 7.62×39mm, flatter trajectory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advantageOver 7.62×39mm Context triple: [6.5 Grendel, advantageOver 7.62×39mm, flatter trajectory]
-
A.
advantageOver 5.56×45mm NATO
Indicates that one entity possesses a superior quality, performance, or benefit in comparison to the 5.56×45mm NATO round.
-
B.
powerComparedToLongGun
Indicates how the power or effectiveness of something compares relative to that of a long gun.
-
C.
Berdan No.1 rifle
Indicates that an entity is a Berdan No.1 rifle, i.e., it has the identity or classification of that specific rifle model.
-
D.
isServiceRifleOf
Indicates that one entity is the designated service rifle used by another entity, typically a military or armed force.
-
E.
ammunitionType
Indicates the specific kind or category of ammunition associated with or used by an 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_69f64ee0c2788190a94a04ad1902fd5e |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64e36c57c8190af09470a8d35512b |
completed | May 2, 2026, 7:19 p.m. |
Created at: April 27, 2026, 11:39 p.m.