Triple
T570172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania courts |
E13643
|
entity |
| Predicate | selectionMethodForJudges |
P126
|
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: [Pennsylvania courts, selectionMethodForJudges, partisan election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionMethodForJudges Context triple: [Pennsylvania courts, selectionMethodForJudges, partisan election]
-
A.
styleOfJudges
Indicates the characteristic manner or approach that judges use when performing their judging role.
-
B.
numberOfJudges
Indicates the total count of judges associated with a particular case, event, or entity.
-
C.
judgesTerm
Indicates that one entity formally evaluates or makes a judgment about a specific term or expression.
-
D.
selectionMethodChangedBy
Indicates that one entity causes or is responsible for a change in the method or criteria used to make a selection.
-
E.
selectionProcess
chosen
Indicates the procedure or set of steps by which one or more options are evaluated and chosen from a larger set of candidates.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b057e708190b4e5975516e58993 |
completed | March 1, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69a494c2caac819086ab316fa49d324c |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.