Triple
T16077985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan Rules of Evidence |
E390023
|
entity |
| Predicate | hasSection |
P35
|
FINISHED |
| Object |
MRE 802
MRE 802 is the Michigan evidentiary rule that sets out the general prohibition against hearsay in Michigan courts.
|
E1194189
|
NE FINISHED |
How this triple was built (4 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: MRE 802 | Statement: [Michigan Rules of Evidence, hasSection, MRE 802]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MRE 802 Context triple: [Michigan Rules of Evidence, hasSection, MRE 802]
-
A.
MRE 801
MRE 801 is a provision of the Michigan Rules of Evidence that defines and governs the concept of hearsay and related terminology in Michigan courts.
-
B.
MRE 702
MRE 702 is a Michigan rule of evidence that governs the admissibility of expert witness testimony in court proceedings.
-
C.
MRE 901
MRE 901 is a rule within the Michigan Rules of Evidence that governs the authentication and identification of evidence before it can be admitted in court.
-
D.
MRE 401
MRE 401 is the Michigan rule of evidence that defines what constitutes relevant evidence in Michigan courts.
-
E.
MRE
MRE is the standard abbreviation used to refer to the Michigan Rules of Evidence, which govern the admissibility and use of evidence in Michigan courts.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: MRE 802 Triple: [Michigan Rules of Evidence, hasSection, MRE 802]
Generated description
MRE 802 is the Michigan evidentiary rule that sets out the general prohibition against hearsay in Michigan courts.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: MRE 802 Target entity description: MRE 802 is the Michigan evidentiary rule that sets out the general prohibition against hearsay in Michigan courts.
-
A.
MRE 801
MRE 801 is a provision of the Michigan Rules of Evidence that defines and governs the concept of hearsay and related terminology in Michigan courts.
-
B.
MRE 702
MRE 702 is a Michigan rule of evidence that governs the admissibility of expert witness testimony in court proceedings.
-
C.
MRE 901
MRE 901 is a rule within the Michigan Rules of Evidence that governs the authentication and identification of evidence before it can be admitted in court.
-
D.
MRE 401
MRE 401 is the Michigan rule of evidence that defines what constitutes relevant evidence in Michigan courts.
-
E.
MRE
MRE is the standard abbreviation used to refer to the Michigan Rules of Evidence, which govern the admissibility and use of evidence in Michigan courts.
- F. None of above. chosen
Provenance (5 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e183c401a881908fcb0b753d2dfc8a |
completed | April 17, 2026, 12:50 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffeb917b008190b1680b347cfa0892 |
completed | May 10, 2026, 2:21 a.m. |
| NEDg | Description generation | batch_69ffecb8c71481908b4913bb078b6415 |
completed | May 10, 2026, 2:26 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ffed469a5c8190932fa4ebc44358c4 |
completed | May 10, 2026, 2:28 a.m. |
Created at: April 10, 2026, 4:57 a.m.