Triple
T25328431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magistrate courts of Georgia |
E635080
|
entity |
| Predicate | magistrateJudgesSelectedBy |
P115795
|
FINISHED |
| Object | 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: election | Statement: [Magistrate courts of Georgia, magistrateJudgesSelectedBy, election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magistrateJudgesSelectedBy Context triple: [Magistrate courts of Georgia, magistrateJudgesSelectedBy, election]
-
A.
magistratesMethodOfSelection
chosen
Indicates how magistrates are chosen or appointed to their positions.
-
B.
hasMagistrateJudges
Indicates that one legal jurisdiction, court, or governing body includes or is served by one or more magistrate judges.
-
C.
magistrateOf
Indicates that a person holds the official position or role of magistrate in relation to a particular jurisdiction, institution, or group.
-
D.
hasMagistrate
Indicates that an entity is under the authority, jurisdiction, or oversight of a specific magistrate.
-
E.
magistrateJudgeTerm
Indicates that a magistrate judge holds or serves a specific judicial term or period of office.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497c2c7b081909a09153061b01fa7 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:30 p.m.