Triple
T3392883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article VIII – Hearsay |
E71459
|
entity |
| Predicate | definesIn |
P23699
|
FINISHED |
| Object | Rule 801(c) hearsay |
—
|
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: Rule 801(c) hearsay | Statement: [Article VIII – Hearsay, definesIn, Rule 801(c) hearsay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesIn Context triple: [Article VIII – Hearsay, definesIn, Rule 801(c) hearsay]
-
A.
areDefinedIn
chosen
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
B.
defined
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
-
C.
definedVia
Indicates that one entity is specified, characterized, or given its meaning by reference to another entity or construct.
-
D.
definedOn
Indicates that something (such as a function, rule, or structure) is specified to apply or be valid over a particular domain, set, or context.
-
E.
definesUseOf
Indicates that one entity specifies or determines how another entity is to be used or applied.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb851e57c8190983cadcedc58db50 |
completed | March 8, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.