Triple
T271356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multnomah County Circuit Court |
E5639
|
entity |
| Predicate | handlesCaseType |
P4217
|
FINISHED |
| Object | civil cases |
—
|
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: civil cases | Statement: [Multnomah County Circuit Court, handlesCaseType, civil cases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesCaseType Context triple: [Multnomah County Circuit Court, handlesCaseType, civil cases]
-
A.
hasTypeOfCase
chosen
Indicates that an entity is associated with or classified under a particular type or category of case.
-
B.
hasCase
Indicates that one entity is involved in, associated with, or characterized by a particular case, instance, or occurrence represented by another entity.
-
C.
specialCaseOf
Indicates that one entity represents a more specific, exceptional, or restricted instance of the general situation, rule, or relationship expressed by another entity.
-
D.
hasJurisdictionOver
Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
-
E.
hasOverrulingCase
Indicates that one legal case supersedes or nullifies the authority or precedent of another case.
- 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25e69a9248190b9e7959b43223baa |
completed | Feb. 28, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69a25b721180819080d43c43fcbccf87 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.