Triple
T3449368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magisterial District Courts of Pennsylvania |
E72755
|
entity |
| Predicate | judgesElectionType |
P19539
|
FINISHED |
| Object | partisan 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: partisan election | Statement: [Magisterial District Courts of Pennsylvania, judgesElectionType, partisan election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judgesElectionType Context triple: [Magisterial District Courts of Pennsylvania, judgesElectionType, partisan 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.
hasJudgeType
Indicates that an entity is associated with a specific category or type of judge.
-
D.
judgesMayBe
Indicates that certain individuals can serve in the role of judges under specified conditions or classifications.
-
E.
hasJuryType
Indicates that an entity is associated with, or classified by, a specific type or category of jury.
- 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_69ad85b05c848190b7a28ceec2bd7b74 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba71f4a4819089d08b871cc9b16f |
completed | March 8, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69adae0255b48190a9069f7871c7a012 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.