Triple
T33140714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Scott, 1st Earl of Eldon |
E848139
|
entity |
| Predicate | termStartAsLordChancellor |
P58625
|
FINISHED |
| Object | 1801 |
—
|
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: 1801 | Statement: [John Scott, 1st Earl of Eldon, termStartAsLordChancellor, 1801]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termStartAsLordChancellor Context triple: [John Scott, 1st Earl of Eldon, termStartAsLordChancellor, 1801]
-
A.
startTimeAsLordChancellor
chosen
Indicates the point in time at which an individual begins serving in the role of Lord Chancellor.
-
B.
termStartAsLordChamberlain
Indicates that an individual begins their period of service holding the position of Lord Chamberlain.
-
C.
termStartAsChancellor
Indicates the date or point in time when an individual begins their term serving in the role of chancellor.
-
D.
endTimeAsLordChancellor
Indicates the point in time at which an individual’s tenure or service as Lord Chancellor comes to an end.
-
E.
termStartAsChancellorOfTheExchequer
Indicates the date or point in time when an individual begins serving in the role of Chancellor of the Exchequer.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:28 a.m.