Triple
T28221504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferguson rifle |
E711468
|
entity |
| Predicate | innovationComparedTo |
P116408
|
FINISHED |
| Object | Brown Bess musket |
—
|
NE NERFINISHED |
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: Brown Bess musket | Statement: [Ferguson rifle, innovationComparedTo, Brown Bess musket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: innovationComparedTo Context triple: [Ferguson rifle, innovationComparedTo, Brown Bess musket]
-
A.
innovationLevel
Indicates the degree or extent to which something is new, original, or creatively advanced compared to existing norms or solutions.
-
B.
innovationFrom
Indicates that something originates, arises, or is derived as an innovation from a particular source or prior entity.
-
C.
technologyLevelComparedTo
chosen
Indicates how the technological advancement of one entity compares relative to that of another entity.
-
D.
technologyLevelComparedToPredecessor
Indicates how the technology level of an entity compares to that of its immediate predecessor.
-
E.
innovation
Indicates the introduction or development of something new or significantly improved compared to existing methods, products, or ideas.
- 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64351ed64819097b557edd9fa37e1 |
completed | May 2, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:46 p.m.