Triple
T32836137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Small Claims Courts |
E839837
|
entity |
| Predicate | timeToHearing |
P94741
|
FINISHED |
| Object | shorter than regular civil docket |
—
|
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: shorter than regular civil docket | Statement: [Iowa Small Claims Courts, timeToHearing, shorter than regular civil docket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeToHearing Context triple: [Iowa Small Claims Courts, timeToHearing, shorter than regular civil docket]
-
A.
hearingSchedule
Indicates that a formal hearing or legal proceeding is scheduled to occur at a specified time and/or place.
-
B.
oralHearingsEndDate
Indicates the date on which the oral hearings in a proceeding or case are concluded.
-
C.
heardByCourt
Indicates that a matter, case, or issue has been formally considered or examined by a court.
-
D.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
E.
resolutionTime
chosen
Indicates the duration taken to resolve an issue, task, or request from its initiation to its completion.
- 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:16 a.m.