Triple
T23724500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Model 1892 Springfield |
E586231
|
entity |
| Predicate | originatingArmory |
P89764
|
FINISHED |
| Object | United States Springfield Armory |
—
|
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: United States Springfield Armory | Statement: [U.S. Model 1892 Springfield, originatingArmory, United States Springfield Armory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatingArmory Context triple: [U.S. Model 1892 Springfield, originatingArmory, United States Springfield Armory]
-
A.
armory
Indicates that an entity serves as a place where weapons, armor, or military equipment are stored, maintained, or supplied for use.
-
B.
armamentStores
Indicates that one entity stores, houses, or contains armaments or weapons for another entity or for a particular purpose.
-
C.
dissolvedAsArmory
Indicates that an organization or entity ceased to exist specifically in its role or function as an armory.
-
D.
armamentOrigin
chosen
Indicates the source or place from which a weapon or armament originates or is supplied.
-
E.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b91364208190b3404534a7403e08 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:07 p.m.