Triple
T22608955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Blount, Lord Mountjoy |
E566639
|
entity |
| Predicate | positionHeld |
P8
|
FINISHED |
| Object | Master of the Ordnance |
—
|
NE NERFINISHED |
How this triple was built (3 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: Master of the Ordnance | Statement: [Charles Blount, Lord Mountjoy, positionHeld, Master of the Ordnance]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Master of the Ordnance Context triple: [Charles Blount, Lord Mountjoy, positionHeld, Master of the Ordnance]
-
A.
Storekeeper of the Ordnance
The Storekeeper of the Ordnance was a senior administrative officer responsible for managing and overseeing the storage, maintenance, and issue of military supplies and equipment for the British Board of Ordnance.
-
B.
Master of the Artillery of Scotland
The Master of the Artillery of Scotland was a senior royal military office responsible for overseeing the kingdom’s artillery, munitions, and related siege equipment.
-
C.
Inspekteur des Heeres
Inspekteur des Heeres is the highest-ranking officer and professional head of the German Army within the Bundeswehr, responsible for its readiness, training, and overall leadership.
-
D.
Clerk of the Ordnance
The Clerk of the Ordnance was a senior administrative officer responsible for managing records, finances, and paperwork for Britain’s Board of Ordnance, which oversaw military supplies, artillery, and fortifications.
-
E.
Master-General of the Ordnance
The Master-General of the Ordnance was a senior British military and governmental office responsible for overseeing artillery, fortifications, military supplies, and related engineering.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Master of the Ordnance Target entity description: Master of the Ordnance was a senior English Crown office responsible for overseeing artillery, munitions, and military supplies, particularly within the Board of Ordnance.
-
A.
Storekeeper of the Ordnance
The Storekeeper of the Ordnance was a senior administrative officer responsible for managing and overseeing the storage, maintenance, and issue of military supplies and equipment for the British Board of Ordnance.
-
B.
Master of the Artillery of Scotland
The Master of the Artillery of Scotland was a senior royal military office responsible for overseeing the kingdom’s artillery, munitions, and related siege equipment.
-
C.
Inspekteur des Heeres
Inspekteur des Heeres is the highest-ranking officer and professional head of the German Army within the Bundeswehr, responsible for its readiness, training, and overall leadership.
-
D.
Clerk of the Ordnance
The Clerk of the Ordnance was a senior administrative officer responsible for managing records, finances, and paperwork for Britain’s Board of Ordnance, which oversaw military supplies, artillery, and fortifications.
-
E.
Master-General of the Ordnance
The Master-General of the Ordnance was a senior British military and governmental office responsible for overseeing artillery, fortifications, military supplies, and related engineering.
- F. None of above. chosen
Provenance (2 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_69e245884860819081046ce07d5872c4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f167e86794819097e9c1ea83db52e6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 2:56 p.m.