Triple
T36897482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Criminal Division (Macomb County Circuit Court) |
E911929
|
entity |
| Predicate | caseSources |
P186659
|
FINISHED |
| Object | lower district courts in Macomb County |
—
|
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: lower district courts in Macomb County | Statement: [Criminal Division (Macomb County Circuit Court), caseSources, lower district courts in Macomb County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseSources Context triple: [Criminal Division (Macomb County Circuit Court), caseSources, lower district courts in Macomb County]
-
A.
caseTypes
Indicates the types or categories of cases associated with or applicable to an entity or situation.
-
B.
usesCase
Indicates that one entity employs, applies, or makes practical use of another entity for a particular purpose or function.
-
C.
caseRecords
Indicates that there exist documented records associated with a particular case or legal proceeding.
-
D.
caseLocation
Indicates the specific place or jurisdiction in which a case or legal matter is situated, filed, or adjudicated.
-
E.
caseNumber
Indicates the unique identifying number assigned to a particular legal or administrative case.
- F. None of above. chosen
Provenance (4 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.