Triple
T6900307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia superior courts |
E159477
|
entity |
| Predicate | judgeElectionType |
P19539
|
FINISHED |
| Object | nonpartisan election |
—
|
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: nonpartisan election | Statement: [Georgia superior courts, judgeElectionType, nonpartisan election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judgeElectionType Context triple: [Georgia superior courts, judgeElectionType, nonpartisan election]
-
A.
hasElectionType
chosen
Indicates the specific category or kind of election associated with a given electoral event or process.
-
B.
appliesToElectionType
Indicates that a rule, condition, or attribute is relevant or applicable to a specific type or category of election.
-
C.
electionMethod
Indicates the process or system used to select a candidate or make a decision in an election.
-
D.
electionSystemFeature
Indicates that an election system possesses a specific characteristic, mechanism, or procedural feature related to how elections are conducted or managed.
-
E.
isDirectElection
Indicates that an official or representative is chosen directly by voters rather than by an intermediary body or electoral college.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d95f26a08190ac9a5068433ef603 |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.