Triple
T25740383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Sumption |
E648198
|
entity |
| Predicate | appointedToPositionBy |
P165320
|
FINISHED |
| Object | David Cameron |
—
|
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: David Cameron | Statement: [Baron Sumption, appointedToPositionBy, David Cameron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedToPositionBy Context triple: [Baron Sumption, appointedToPositionBy, David Cameron]
-
A.
appointedFrom
Indicates that an entity was selected or assigned to a position or role originating from a specified source, body, or prior position.
-
B.
appointedIn
Indicates that an entity is formally assigned or designated to a role, position, or office within a specific context, organization, or jurisdiction.
-
C.
appointedToFillVacancyOf
Indicates that one entity has been officially selected to occupy a position or role that was previously left vacant by another entity.
-
D.
appointedAfter
Indicates that one entity was appointed to a position or role at a later time than another entity.
-
E.
appointedWith
Indicates that one entity has been formally assigned or designated to a role, position, or responsibility in relation to another entity.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 22, 2026, 3:42 a.m.