Triple
T25202369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Dakota municipal courts |
E631154
|
entity |
| Predicate | casesInvolve |
P81213
|
FINISHED |
| Object | minor criminal complaints |
—
|
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: minor criminal complaints | Statement: [North Dakota municipal courts, casesInvolve, minor criminal complaints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casesInvolve Context triple: [North Dakota municipal courts, casesInvolve, minor criminal complaints]
-
A.
caseRecords
Indicates that there exist documented records associated with a particular case or legal proceeding.
-
B.
caseTypes
chosen
Indicates the types or categories of cases associated with or applicable to an entity or situation.
-
C.
involvesIssue
Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
-
D.
disputeInvolves
Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
-
E.
constantInvolved
Indicates that a constant participates in or is directly involved in the specified relation, operation, or context.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f474b904f48190be6513788f89c6a9 |
completed | May 1, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 12:51 p.m.