Triple
T29984246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur William Acland Hood |
E761684
|
entity |
| Predicate | appointedAsFirstNavalLord |
P181329
|
FINISHED |
| Object | 1885 |
—
|
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: 1885 | Statement: [Arthur William Acland Hood, appointedAsFirstNavalLord, 1885]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsFirstNavalLord Context triple: [Arthur William Acland Hood, appointedAsFirstNavalLord, 1885]
-
A.
firstLordOfTheAdmiralty
Indicates that an entity holds or has held the position of First Lord of the Admiralty in relation to a governing body or navy.
-
B.
appointedChiefOfNavalGeneralStaff
Indicates that an entity has been formally appointed to the position of Chief of the Naval General Staff for another entity (such as a state, navy, or military organization).
-
C.
appointedAdmiralOfTheBlue
Indicates that someone was formally given the naval rank or position of Admiral of the Blue.
-
D.
tenureAsFirstSeaLordStart
Indicates the date on which an individual began serving in the role of First Sea Lord.
-
E.
admiralOfFleet
Indicates a relationship where a person holds the highest naval rank or command position over an entire fleet.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
| PDg | Predicate description generation | batch_69f7688cea58819098bdfd7c80df7634 |
completed | May 3, 2026, 3:23 p.m. |
Created at: April 29, 2026, 6:36 p.m.