Triple
T4267611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idaho Supreme Court |
E96862
|
entity |
| Predicate | isFinalArbiterOf |
P55088
|
FINISHED |
| Object | Idaho state law issues subject to federal review |
—
|
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: Idaho state law issues subject to federal review | Statement: [Idaho Supreme Court, isFinalArbiterOf, Idaho state law issues subject to federal review]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFinalArbiterOf Context triple: [Idaho Supreme Court, isFinalArbiterOf, Idaho state law issues subject to federal review]
-
A.
finalRuler
Indicates that an entity is the last or ultimate ruler of another entity, with no subsequent rulers following.
-
B.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
-
C.
decidedWith
Indicates that an entity made a decision jointly or in agreement with another entity.
-
D.
hasJudge
Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
-
E.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34fce710481909d90ed4a3d150fde |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:07 p.m.