Triple
T29116757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wyoming Supreme Court |
E737065
|
entity |
| Predicate | termLengthForJustices |
P73788
|
FINISHED |
| Object | 8 years |
—
|
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: 8 years | Statement: [Wyoming Supreme Court, termLengthForJustices, 8 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termLengthForJustices Context triple: [Wyoming Supreme Court, termLengthForJustices, 8 years]
-
A.
termLengthOfJustices
chosen
Indicates the duration of time that justices serve in their official positions.
-
B.
endTimeForPosition_AssociateJustice
Indicates the time at which an individual's tenure in the position of Associate Justice concludes.
-
C.
hasLifeTenureJudges
Indicates that the judges associated with an office, position, or institution hold their roles for life, typically remaining in office until they choose to retire, resign, or are removed under exceptional circumstances.
-
D.
maximumAgeOfJudges
Indicates the highest allowable age that individuals may have in order to serve as judges.
-
E.
numberOfAssociateJustices
Indicates the total count of associate justices associated with a given judicial body or court.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661f1378c8190aa0ffc365dfb589f |
completed | May 2, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:22 a.m.