Triple
T14165229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock Island Arsenal |
E351054
|
entity |
| Predicate | hasMuseumCollectionFocus |
P113082
|
FINISHED |
| Object | U.S. Army ordnance and small arms history |
—
|
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: U.S. Army ordnance and small arms history | Statement: [Rock Island Arsenal, hasMuseumCollectionFocus, U.S. Army ordnance and small arms history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMuseumCollectionFocus Context triple: [Rock Island Arsenal, hasMuseumCollectionFocus, U.S. Army ordnance and small arms history]
-
A.
hasMuseumFunction
Indicates that an entity serves the role or performs the function of a museum.
-
B.
hasMuseumComponent
Indicates that something includes, contains, or is composed of a museum or museum-related part as one of its components.
-
C.
hasMuseumType
Indicates that an entity is classified as a museum of a specific type or category.
-
D.
hasExhibitionFocus
Indicates that an exhibition is primarily centered on, or thematically dedicated to, a particular subject, medium, or focus area.
-
E.
hasMuseumAt
Indicates that a museum is located at or exists in a specified place or location.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b207cc8190b85b1ff0910b54da |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 12:59 a.m.