Triple
T32344929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tucker |
E826430
|
entity |
| Predicate | caseOriginatedFrom |
P8824
|
FINISHED |
| Object | Michigan state criminal prosecution |
—
|
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: Michigan state criminal prosecution | Statement: [Tucker, caseOriginatedFrom, Michigan state criminal prosecution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseOriginatedFrom Context triple: [Tucker, caseOriginatedFrom, Michigan state criminal prosecution]
-
A.
originatedInCourt
Indicates that a legal case, decision, or proceeding began or was first filed in a specified court.
-
B.
originatingJurisdiction
Indicates the jurisdiction (such as a country, state, or legal authority) from which something originally comes or under whose laws it was first established.
-
C.
originatedInCourtOf
Indicates that a legal case, decision, or proceeding began or was first filed in a specified court.
-
D.
originatingStateCourt
chosen
Indicates the court in which a legal case or proceeding was originally filed or initiated.
-
E.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be28d7008190a10138a08a0ec643 |
completed | May 3, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:48 a.m.