Triple
T8158699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon appellate courts |
E190517
|
entity |
| Predicate | reviewStandardIncludes |
P19701
|
FINISHED |
| Object | de novo review (in some issues) |
—
|
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: de novo review (in some issues) | Statement: [Oregon appellate courts, reviewStandardIncludes, de novo review (in some issues)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reviewStandardIncludes Context triple: [Oregon appellate courts, reviewStandardIncludes, de novo review (in some issues)]
-
A.
includesStandard
chosen
Indicates that one entity contains, incorporates, or makes use of a particular standard as part of its definition, implementation, or specification.
-
B.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
C.
outputIncludes
Indicates that the result or product of a process, function, or action contains or incorporates a specified element or component.
-
D.
coreStandard
Indicates that something conforms to, is defined by, or is governed by a central or foundational standard or specification.
-
E.
reportsInStandard
Indicates that something is reported or presented according to a specified standard or standardized format.
- 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb455213f08190a4327a2116c7381f |
completed | March 31, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:38 p.m.