Triple
T13859786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Chatham |
E333159
|
entity |
| Predicate | hasTitleHolderOccupation |
P105981
|
FINISHED |
| Object | Prime Minister of Great Britain |
—
|
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: Prime Minister of Great Britain | Statement: [Baron Chatham, hasTitleHolderOccupation, Prime Minister of Great Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleHolderOccupation Context triple: [Baron Chatham, hasTitleHolderOccupation, Prime Minister of Great Britain]
-
A.
hasTitleHolder
Indicates that one entity is the current or designated holder of a specific title, position, or honor associated with another entity.
-
B.
originalHolderOccupation
Indicates the occupation or professional role held by the entity that originally possessed or owned another entity.
-
C.
hasTitleHolderResidence
Indicates that a specified residence is the official home or dwelling place of the current holder of a particular title.
-
D.
holderIsOccupation
chosen
Indicates that the holder entity has the specified occupation or job role.
-
E.
holderFullTitle
Indicates that one entity is the complete, formal title or designation held by another entity.
- 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02de38e48190b6ead95561031c32 |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.