Triple
T11101206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franklin County Court of Common Pleas |
E262506
|
entity |
| Predicate | caseCategories |
P81213
|
FINISHED |
| Object | civil |
—
|
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 | Statement: [Franklin County Court of Common Pleas, caseCategories, civil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseCategories Context triple: [Franklin County Court of Common Pleas, caseCategories, civil]
-
A.
caseTypes
chosen
Indicates the types or categories of cases associated with or applicable to an entity or situation.
-
B.
caseManagement
Indicates that one entity is responsible for coordinating, organizing, and overseeing services or actions provided to another entity within a managed process or case.
-
C.
legalCase
Indicates a relationship where a formal legal dispute or proceeding exists between parties, typically adjudicated by a court or similar authority.
-
D.
limitsCategory
Indicates that one entity restricts or constrains the scope, type, or category of another entity.
-
E.
coreCategory
Indicates that one entity is the primary or fundamental category to which another entity belongs or is classified under.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a2ab09081908ffce2df8912b657 |
completed | April 9, 2026, 12:23 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.