Triple
T1198654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. President |
E25725
|
entity |
| Predicate | headOfStateAddress |
P25729
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mr. President, headOfStateAddress, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headOfStateAddress Context triple: [Mr. President, headOfStateAddress, yes]
-
A.
residenceOfHeadOfGovernment
Indicates the place where the head of government officially resides.
-
B.
seatOfGovernment
Indicates that a location serves as the administrative center where a government exercises its official authority and conducts its primary governing functions.
-
C.
headOfStateOf
Indicates that one entity serves as the chief public representative and highest-ranking official authority of another entity, typically a country or state.
-
D.
seatOfPlenipotentiaryRepresentative
Indicates the location or institution that serves as the official base or office for a plenipotentiary representative.
-
E.
headOfStateIs
Indicates that one entity serves as the head of state (the highest public representative) of another entity, typically a country or similar political unit.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9c013c8190822d44d465d60fdb |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc49693c8190978ec63a5171d342 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:46 p.m.