Triple
T23925412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. politicians |
E602337
|
entity |
| Predicate | areElectedOrAppointed |
P11399
|
FINISHED |
| Object | elected |
—
|
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: elected | Statement: [U.S. politicians, areElectedOrAppointed, elected]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areElectedOrAppointed Context triple: [U.S. politicians, areElectedOrAppointed, elected]
-
A.
appointedOrElected
chosen
Indicates that an entity attained a position, role, or office through either an appointment process or an electoral process.
-
B.
isElectoralOffice
Indicates that the referenced position or role is an official public office filled through an electoral process.
-
C.
executiveElectedBy
Indicates that an executive assumes office as a result of being chosen through a formal election conducted by a specified person, group, or body.
-
D.
hasElectoralDignityIn
Indicates that an entity holds or possesses electoral authority, status, or office within a specified political or electoral jurisdiction.
-
E.
appointedIn
Indicates that an entity is formally assigned or designated to a role, position, or office within a specific context, organization, or jurisdiction.
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf1ce7f88190a4afd091b4384558 |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:44 p.m.