Triple
T5478379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terry v. Ohio |
E123410
|
entity |
| Predicate | standardOfProofUsed |
P6737
|
FINISHED |
| Object | reasonable suspicion |
—
|
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: reasonable suspicion | Statement: [Terry v. Ohio, standardOfProofUsed, reasonable suspicion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardOfProofUsed Context triple: [Terry v. Ohio, standardOfProofUsed, reasonable suspicion]
-
A.
standardOfProof
chosen
Indicates the level or degree of certainty required to establish that a claim or allegation is true in a given context.
-
B.
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.
-
C.
usedEvidenceType
Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
-
D.
convictedBy
Indicates that an authority, typically a court or judge, has formally found an entity guilty of a crime or offense.
-
E.
reasonForConviction
Indicates the specific offense or legal basis for which an individual was found guilty or convicted.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9247a16c8190ac5a02534da48853 |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.