Triple
T25631718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal President a. D. |
E642592
|
entity |
| Predicate | officeHolderStatus |
P172320
|
FINISHED |
| Object | former office holder |
—
|
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: former office holder | Statement: [Federal President a. D., officeHolderStatus, former office holder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeHolderStatus Context triple: [Federal President a. D., officeHolderStatus, former office holder]
-
A.
officeHolderIs
Indicates that one entity serves as the office holder (e.g., official or position occupant) of another entity, such as an office, role, or institution.
-
B.
officeHolderMayBe
Indicates that a specified person is permitted or eligible to hold a particular office or position.
-
C.
officeHolderOf
Indicates that a person holds or has held an official position or role within a specified organization, institution, or office.
-
D.
officeHolderAsOf
Indicates that a person holds or held a specific office or position as of a particular date or point in time.
-
E.
officeHolderUsually
Indicates that an entity is the person who typically or customarily holds a particular office or position.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 21, 2026, 5:18 p.m.