Triple
T5947740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Lamont of Lerwick |
E132320
|
entity |
| Predicate | titleHolderChancellorshipStart |
P58625
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Baron Lamont of Lerwick, titleHolderChancellorshipStart, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderChancellorshipStart Context triple: [Baron Lamont of Lerwick, titleHolderChancellorshipStart, 1990]
-
A.
chancellorTitle
Indicates the official title or designation held by an individual serving in the role of chancellor.
-
B.
startTimeAsLordChancellor
chosen
Indicates the point in time at which an individual begins serving in the role of Lord Chancellor.
-
C.
precededInOfficeAsChancellorBy
Indicates that one individual assumed the role of Chancellor after another specific individual, who held the office immediately before them.
-
D.
firstOfficeHolderStart
Indicates the date or time when the first person to hold a particular office or position began their term.
-
E.
lastChancellor
Indicates that one entity served as the most recent chancellor of another entity (such as a country, institution, or organization).
- 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_69c00869d3308190af89b2453e0f7546 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0335806788190b6488ca8b73f7a63 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:01 p.m.