Triple
T29913446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Rules of Evidence |
E759729
|
entity |
| Predicate | providesExceptionsFor |
P68180
|
FINISHED |
| Object | hearsay rule |
—
|
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: hearsay rule | Statement: [Washington Rules of Evidence, providesExceptionsFor, hearsay rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesExceptionsFor Context triple: [Washington Rules of Evidence, providesExceptionsFor, hearsay rule]
-
A.
doesNotProvideExceptionFor
Indicates that one party or rule fails to grant an exemption, special case, or exclusion to another party or situation.
-
B.
providesExemptionsTo
chosen
Indicates that one entity grants or offers exemptions, waivers, or exceptions from rules, obligations, or requirements to another entity.
-
C.
hasExceptionFor
Indicates that a general rule, condition, or behavior does not apply in a particular case or under specific circumstances.
-
D.
includesException
Indicates that one entity explicitly contains, references, or accounts for a specified exception within its definition, behavior, or processing.
-
E.
canBeThrownBy
Indicates that one entity is capable of being thrown or launched 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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 29, 2026, 6:11 p.m.