Triple
T11727551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Cloud |
E278810
|
entity |
| Predicate | office held by head of government |
P27990
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Michael Cloud, office held by head of government, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: office held by head of government Context triple: [Michael Cloud, office held by head of government, none]
-
A.
headOfOffice
Indicates that one entity serves as the chief or leading authority in charge of a particular office or organizational unit.
-
B.
headOfGovernmentForOffice
chosen
Indicates that a person serves as the head of government corresponding to a specific governmental office or position.
-
C.
headOfGovernment
Indicates that one entity serves as the chief executive authority or leader of the government of another entity.
-
D.
headOfGovernmentBody
Indicates that one entity serves as the chief executive or leading official in charge of governing another entity, typically a political or administrative body.
-
E.
headOfGovernmentBranch
Indicates that one entity serves as the chief leader or top executive authority of a particular branch of government.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4d70d908190b5f47c2ef501a191 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.