Triple
T28353977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .577 Snider |
E718173
|
entity |
| Predicate | originalLoading |
P160482
|
FINISHED |
| Object | paper-lined brass case with black powder charge |
—
|
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: paper-lined brass case with black powder charge | Statement: [.577 Snider, originalLoading, paper-lined brass case with black powder charge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalLoading Context triple: [.577 Snider, originalLoading, paper-lined brass case with black powder charge]
-
A.
loader
Indicates a relationship where an entity is responsible for loading or placing items, data, or resources into another system, container, or context.
-
B.
originalRelease
Indicates the initial publication or first official release event of a work or product.
-
C.
loadedWith
chosen
Indicates that one entity is carrying, filled with, or heavily supplied with another entity.
-
D.
originalFor
Indicates that one entity serves as the source, basis, or prototype from which another entity is derived, adapted, or created.
-
E.
loadingMechanism
Indicates the method or system by which something is loaded into or onto another object or structure.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: April 28, 2026, 12:48 a.m.