Triple
T11209405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macomb County Circuit Court |
E265263
|
entity |
| Predicate | handlesFelonyCases |
P87324
|
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: [Macomb County Circuit Court, handlesFelonyCases, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesFelonyCases Context triple: [Macomb County Circuit Court, handlesFelonyCases, yes]
-
A.
hasCriminalJurisdictionOver
Indicates that one authority or legal body holds the power to investigate, prosecute, and adjudicate criminal offenses committed within a specified scope or territory in relation to another entity.
-
B.
hearsCriminalCases
chosen
Indicates that a legal authority or court is responsible for listening to and adjudicating criminal cases.
-
C.
haveCriminalLaw
Indicates that an entity possesses, applies, or is governed by a system or body of criminal law.
-
D.
crimeCharged
Indicates that legal authorities have formally accused an entity of committing a specific crime.
-
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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d5f8908190903817f84c629ba1 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.