Triple
T27229988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springfield Model 1863 rifle-musket |
E682126
|
entity |
| Predicate | typicalBayonet |
P37995
|
FINISHED |
| Object | socket bayonet |
—
|
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: socket bayonet | Statement: [Springfield Model 1863 rifle-musket, typicalBayonet, socket bayonet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBayonet Context triple: [Springfield Model 1863 rifle-musket, typicalBayonet, socket bayonet]
-
A.
typicalWeapon
Indicates that the object is a weapon commonly or characteristically used by the subject.
-
B.
bayonetMount
chosen
Indicates that one object is equipped with or designed to accept a bayonet-style mounting connection to another object.
-
C.
typicalOrdnance
Indicates that something is a standard or commonly used type of weaponry or munitions associated with a given entity or context.
-
D.
bladeType
Indicates the specific kind or category of blade associated with an object or entity.
-
E.
boltType
Indicates the specific kind or category of bolt associated with or used in relation to an entity.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
Created at: April 27, 2026, 9:46 a.m.