Triple
T37328010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ken Clarke |
E926662
|
entity |
| Predicate | succeededInOfficeAsChancellor |
P34719
|
FINISHED |
| Object | Gordon Brown |
—
|
NE NERFINISHED |
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: Gordon Brown | Statement: [Ken Clarke, succeededInOfficeAsChancellor, Gordon Brown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededInOfficeAsChancellor Context triple: [Ken Clarke, succeededInOfficeAsChancellor, Gordon Brown]
-
A.
succeededByAsChancellor
Indicates that one entity directly followed another in the role or office of chancellor.
-
B.
precededInOfficeAsChancellorBy
Indicates that one individual assumed the role of Chancellor after another specific individual, who held the office immediately before them.
-
C.
succeededBy (Chancellor of the Exchequer)
chosen
Indicates that one individual directly followed another in holding the position of Chancellor of the Exchequer.
-
D.
hasChancellor
Indicates that an entity holds the position or role of chancellor for another entity.
-
E.
servedAsHeadOfTheChancelleryFrom
Indicates that a person held the position of head of the chancellery starting from a specified date or time period.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00acf86e4081909aad9356650e0f79 |
completed | May 10, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_6a00ac813fd08190a0a7782609e74e70 |
completed | May 10, 2026, 4:04 p.m. |
Created at: May 3, 2026, 4:16 p.m.