Triple
T37185862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arkansas Court of Appeals |
E921318
|
entity |
| Predicate | decidesCasesBy |
P1033
|
FINISHED |
| Object | majority vote of panel |
—
|
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: majority vote of panel | Statement: [Arkansas Court of Appeals, decidesCasesBy, majority vote of panel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidesCasesBy Context triple: [Arkansas Court of Appeals, decidesCasesBy, majority vote of panel]
-
A.
caseDecidedBy
Indicates that a legal case is resolved or adjudicated by a specific decision-making authority, such as a judge or court.
-
B.
legalCaseHeParticipatedInDecidedBy
Indicates that a legal case in which he participated was decided or adjudicated by a specified authority or court.
-
C.
caseDecidedIn
Indicates that a particular legal case was resolved or adjudicated within a specified court, jurisdiction, or decision-making body.
-
D.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
E.
decides
chosen
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.