Triple
T371067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miranda v. Arizona |
E8268
|
entity |
| Predicate | standardOfWaiver |
P11750
|
FINISHED |
| Object | knowing and intelligent |
—
|
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: knowing and intelligent | Statement: [Miranda v. Arizona, standardOfWaiver, knowing and intelligent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardOfWaiver Context triple: [Miranda v. Arizona, standardOfWaiver, knowing and intelligent]
-
A.
standardOfReview
Indicates the level and type of scrutiny an authority (such as a court or reviewer) applies when evaluating a prior decision, action, or finding.
-
B.
exemptionType
Indicates the specific category or kind of exemption that applies in a given context.
-
C.
standardOfProof
Indicates the level or degree of certainty required to establish that a claim or allegation is true in a given context.
-
D.
standardApplied
Indicates that a particular standard, rule, or guideline has been put into effect or used as the basis for an action or decision in the relationship.
-
E.
mayBeAffirmedRatherThanSworn
Indicates that a statement or testimony can be confirmed by affirmation instead of being given under a formal oath.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebff472881909fad81d597425ea6 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e960d880819084b3df4e5137a1e2 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea0b23ec8190bef9d593162388a4 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.