Triple
T15723940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiral Sir Henry Leach |
E381173
|
entity |
| Predicate | tenureAsFirstSeaLordStart |
P119924
|
FINISHED |
| Object | 1979 |
—
|
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: 1979 | Statement: [Admiral Sir Henry Leach, tenureAsFirstSeaLordStart, 1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tenureAsFirstSeaLordStart Context triple: [Admiral Sir Henry Leach, tenureAsFirstSeaLordStart, 1979]
-
A.
tenureAsEarlStart
Indicates the date or point in time when an individual’s tenure or period of holding the title of Earl begins.
-
B.
termStartAsChancellorOfTheExchequer
Indicates the date or point in time when an individual begins serving in the role of Chancellor of the Exchequer.
-
C.
startTimeAsSecretaryOfTheNavy
Indicates the date and time at which an individual began serving in the role of Secretary of the Navy.
-
D.
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.
-
E.
termStartAsLordChamberlain
Indicates that an individual begins their period of service holding the position of Lord Chamberlain.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb1fdd4819088f3e243263e5f73 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0094af5b481908ad51d5d7ba0c726 |
completed | April 15, 2026, 9:55 p.m. |
Created at: April 10, 2026, 4:46 a.m.