Triple
T7444860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springfield Model 1795 musket |
E171851
|
entity |
| Predicate | boreType |
P52917
|
FINISHED |
| Object | smoothbore |
—
|
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: smoothbore | Statement: [Springfield Model 1795 musket, boreType, smoothbore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boreType Context triple: [Springfield Model 1795 musket, boreType, smoothbore]
-
A.
hasBoreType
chosen
Indicates that an entity is characterized by or associated with a specific type of bore (e.g., cylindrical, tapered, rifled).
-
B.
bore
Indicates that one entity caused another entity to feel uninterested, tired, or lacking in engagement.
-
C.
cylinderBore
Indicates the diameter of the cylindrical chamber (bore) in which a piston or similar component moves.
-
D.
numberOfBores
Indicates the relationship specifying how many bores (e.g., cylindrical holes or channels) are present in or associated with an object.
-
E.
boreSpacing
Indicates the center-to-center distance between adjacent bores or holes in a component or assembly.
- 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_69c68a65402881908f7869368eb746fb |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f37054388190a6cb4c0db2ca6014 |
completed | March 27, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:14 p.m.