Triple
T30397535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wn. App. |
E773259
|
entity |
| Predicate | reporterLevel |
P170761
|
FINISHED |
| Object | intermediate appellate court |
—
|
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: intermediate appellate court | Statement: [Wn. App., reporterLevel, intermediate appellate court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reporterLevel Context triple: [Wn. App., reporterLevel, intermediate appellate court]
-
A.
reporterNumber
Indicates the identifier or count associated with the reporter involved in a given event or relationship.
-
B.
exportLevel
Indicates the degree or extent to which something is produced in one place and sent out or made available to other places or markets.
-
C.
reporterType
Indicates the specific role or category of reporter associated with an entity or event.
-
D.
reporterVolume
Indicates the amount or intensity of content produced or reported by a reporter within a given context or period.
-
E.
loggingLevel
Indicates the severity or detail level at which events or messages are recorded in a logging system.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:03 p.m.