Triple
T24106362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Baron Chelmsford |
E597236
|
entity |
| Predicate | termAsLordChancellorStart |
P58625
|
FINISHED |
| Object | 1858 |
—
|
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: 1858 | Statement: [1st Baron Chelmsford, termAsLordChancellorStart, 1858]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termAsLordChancellorStart Context triple: [1st Baron Chelmsford, termAsLordChancellorStart, 1858]
-
A.
startTimeAsLordChancellor
chosen
Indicates the point in time at which an individual begins serving in the role of Lord Chancellor.
-
B.
endTimeAsLordChancellor
Indicates the point in time at which an individual’s tenure or service as Lord Chancellor comes to an end.
-
C.
termStartAsLordChamberlain
Indicates that an individual begins their period of service holding the position of Lord Chamberlain.
-
D.
termStartAsChancellorOfTheExchequer
Indicates the date or point in time when an individual begins serving in the role of Chancellor of the Exchequer.
-
E.
termEndAsLordChamberlain
Indicates that an entity’s period of service in the role of Lord Chamberlain has concluded at a specified time or under specified conditions.
- 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de170ee88190a6d57482651f7da9 |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:01 p.m.