Triple
T15808234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Court of Appeals |
E383275
|
entity |
| Predicate | hearsCasesInPanels |
P50258
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Iowa Court of Appeals, hearsCasesInPanels, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearsCasesInPanels Context triple: [Iowa Court of Appeals, hearsCasesInPanels, yes]
-
A.
hearsCasesInPanelsOf
chosen
Indicates that a judicial body conducts its case hearings using panels composed of a specified number or configuration of judges.
-
B.
hearsCasesWith
Indicates that one judicial body or judge conducts proceedings together with another judicial body or judge in hearing the same cases.
-
C.
hearsCasesAs
Indicates that one judicial body or judge reviews and adjudicates cases originating from another court or jurisdiction.
-
D.
hearsCasesUnder
Indicates that a judicial body or authority has the responsibility and power to adjudicate legal cases falling within a specified jurisdiction, category, or scope.
-
E.
hearsCasesAgainst
Indicates that one party (typically a judicial body or official) formally listens to and considers legal cases brought against another party.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b52896bc819086ef95cc63e90daa |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:48 a.m.