Triple
T28490455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Henry |
E720948
|
entity |
| Predicate | hasRiflingType |
P53712
|
FINISHED |
| Object | polygonal-like Henry rifling |
—
|
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: polygonal-like Henry rifling | Statement: [Alexander Henry, hasRiflingType, polygonal-like Henry rifling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiflingType Context triple: [Alexander Henry, hasRiflingType, polygonal-like Henry rifling]
-
A.
rifling
chosen
Indicates the presence or action of spiral grooves inside a gun barrel that impart spin to a projectile to stabilize its flight.
-
B.
hasHeavierBarrelThan
Indicates that the barrel of one entity has a greater weight than the barrel of another entity.
-
C.
isGasOperated
Indicates that an entity functions or operates using gas as its primary power or energy source.
-
D.
isServiceRifleOf
Indicates that one entity is the designated service rifle used by another entity, typically a military or armed force.
-
E.
hasFiringRange
Indicates that one entity possesses or provides a designated area or capability for discharging weapons over a specified distance.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 3:01 a.m.