Triple
T26604704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District III |
E667735
|
entity |
| Predicate | appealPathTo |
P13940
|
FINISHED |
| Object | Wisconsin Supreme Court |
—
|
NE NERFINISHED |
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: Wisconsin Supreme Court | Statement: [District III, appealPathTo, Wisconsin Supreme Court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appealPathTo Context triple: [District III, appealPathTo, Wisconsin Supreme Court]
-
A.
appealsGoTo
chosen
Indicates that appeals arising from a decision or judgment are directed to and handled by a specified higher authority or court.
-
B.
pathTo
Indicates that one entity serves as a route, way, or means of reaching, accessing, or moving to another entity.
-
C.
appealBeyond
Indicates that something has significance, relevance, or attractiveness that extends beyond a specified scope, group, or context.
-
D.
appealsFrom
Indicates that a decision, judgment, or ruling is being challenged and taken to a higher authority or court for review.
-
E.
appealsFor
Indicates that one entity formally requests support, intervention, or a favorable decision from another entity.
- 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:14 a.m.