Triple
T15218293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Dallas mayoral election |
E363694
|
entity |
| Predicate | isPartisanBallot |
P117568
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [2019 Dallas mayoral election, isPartisanBallot, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartisanBallot Context triple: [2019 Dallas mayoral election, isPartisanBallot, false]
-
A.
isBipartisan
Indicates that an action, decision, or stance is supported or undertaken by members of two (or more) opposing political parties.
-
B.
ballot
Indicates that an entity participates in a formal voting process, typically by casting or submitting a vote or choice.
-
C.
partyBallotRelationship
Indicates the relationship between a political party and a ballot, such as how the party is represented or listed on that ballot.
-
D.
ballotUnitUsed
Indicates that a particular ballot unit was utilized in the conduct of an election or voting process.
-
E.
partyInElection
Indicates that a political party participates as a contestant or actor in a specific election.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0076f90c481909989befe031a2cae |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:11 a.m.