Triple
T26256952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Washington, D.C., mayoral election |
E656735
|
entity |
| Predicate | mayorAfterParty |
P160171
|
FINISHED |
| Object | Democratic Party |
—
|
NE NERFINISHED |
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: Democratic Party | Statement: [2014 Washington, D.C., mayoral election, mayorAfterParty, Democratic Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayorAfterParty Context triple: [2014 Washington, D.C., mayoral election, mayorAfterParty, Democratic Party]
-
A.
presidentAfterParty
Indicates that one person became president after another person from the same political party.
-
B.
governorAfterParty
Indicates that one governor’s term in office occurred after the tenure of another governor from a specified political party.
-
C.
mayorAppointment
Indicates that one entity appoints or designates another entity to serve in the role of mayor.
-
D.
mayorSelection
Indicates the process or outcome of choosing or appointing someone to serve as mayor of a place.
-
E.
mayorType
Indicates the specific category or role classification of a mayor in relation to their office or jurisdiction.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dfbd8e48190b450a6eb5873f021 |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 9:09 p.m.