Triple
T31308038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York common law courts |
E798387
|
entity |
| Predicate | handledMattersType |
P52843
|
FINISHED |
| Object | legal matters |
—
|
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: legal matters | Statement: [New York common law courts, handledMattersType, legal matters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handledMattersType Context triple: [New York common law courts, handledMattersType, legal matters]
-
A.
handledMatter
Indicates that an entity has dealt with, managed, or taken responsibility for a particular matter, issue, or case.
-
B.
handlesCivilMatter
chosen
Indicates that an entity is responsible for dealing with or adjudicating civil (non-criminal) legal matters involving disputes between parties.
-
C.
handledIn
Indicates that an action, request, or process is managed, processed, or resolved within a particular context, location, system, or jurisdiction.
-
D.
handledWith
Indicates that an entity is managed, processed, or dealt with using a particular method, tool, or means.
-
E.
handledAppeals
Indicates that one party has received, reviewed, and taken action on appeals submitted by another party.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 29, 2026, 9:14 p.m.