Triple
T25626184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canning family |
E642438
|
entity |
| Predicate | hasMemberWhoHeldCabinetOffice |
P112779
|
FINISHED |
| Object | George Canning |
—
|
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: George Canning | Statement: [Canning family, hasMemberWhoHeldCabinetOffice, George Canning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberWhoHeldCabinetOffice Context triple: [Canning family, hasMemberWhoHeldCabinetOffice, George Canning]
-
A.
hasMemberWhoHeldOffice
chosen
Indicates that a group or organization includes at least one member who has held a specified office or position.
-
B.
hadMinisterialPost
Indicates that an entity has held or occupied a ministerial government position or office.
-
C.
servedInCabinetOf
Indicates that one person held a position as a member of the governmental cabinet led by another person.
-
D.
hasMemberWhoServedOn
Indicates that a group or organization includes at least one member who has served on a specified body, committee, or entity.
-
E.
hasListOfOfficeHolders
Indicates that an entity is associated with a collection or record enumerating the individuals who have held a particular office or position.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 21, 2026, 5:14 p.m.