Triple
T33743806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springfield Model 1866 rifle |
E864643
|
entity |
| Predicate | actionOrigin |
P177266
|
FINISHED |
| Object | Erskine S. Allin trapdoor system |
—
|
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: Erskine S. Allin trapdoor system | Statement: [Springfield Model 1866 rifle, actionOrigin, Erskine S. Allin trapdoor system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actionOrigin Context triple: [Springfield Model 1866 rifle, actionOrigin, Erskine S. Allin trapdoor system]
-
A.
actionBy
Indicates that a particular action is performed or carried out by a specified agent or entity.
-
B.
registrationOrigin
Indicates the source or context from which a registration event was initiated or created.
-
C.
missionOrigin
Indicates the place, organization, or context from which a mission is initiated or originates.
-
D.
impactOrigin
Indicates that one entity is the source or cause from which the impact or effect on another entity originates.
-
E.
originSite
Indicates the place or site from which something or someone originally comes or is derived.
- F. None of above. chosen
Provenance (4 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb5c15408190915e27f023429d58 |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fa335b908190a20d92d5396203b5 |
completed | May 3, 2026, 7:33 a.m. |
Created at: May 1, 2026, 1:44 a.m.