Triple
T16958199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Bench |
E411358
|
entity |
| Predicate | handledMatters |
P71354
|
FINISHED |
| Object | common pleas |
—
|
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: common pleas | Statement: [Common Bench, handledMatters, common pleas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handledMatters Context triple: [Common Bench, handledMatters, common pleas]
-
A.
handledMatter
chosen
Indicates that an entity has dealt with, managed, or taken responsibility for a particular matter, issue, or case.
-
B.
handledWith
Indicates that an entity is managed, processed, or dealt with using a particular method, tool, or means.
-
C.
handlesCivilMatter
Indicates that an entity is responsible for dealing with or adjudicating civil (non-criminal) legal matters involving disputes between parties.
-
D.
managedAffairsOf
Indicates that one entity was responsible for handling, overseeing, or conducting the business, administrative, or personal matters of another entity.
-
E.
handles
Indicates that one entity is responsible for dealing with, managing, or taking care of another entity or task.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d01d34d08190a73ce48e9988bd97 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.