Triple
T10800202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commercial Calendar Section |
E254816
|
entity |
| Predicate | caseLevel |
P7279
|
FINISHED |
| Object | law division 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: law division civil cases | Statement: [Commercial Calendar Section, caseLevel, law division civil cases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseLevel Context triple: [Commercial Calendar Section, caseLevel, law division civil cases]
-
A.
letterCase
Indicates the relationship between a character or string and its typographical case (such as uppercase, lowercase, or mixed case).
-
B.
classificationLevel
chosen
Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
-
C.
centralToCase
Indicates that something plays a pivotal or essential role in determining the outcome or understanding of a particular case.
-
D.
caseNumber
Indicates the unique identifying number assigned to a particular legal or administrative case.
-
E.
majorCase
Indicates that a legal case is of primary importance or high significance within a given context.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733366c408190bfd3b57be5ef2440 |
completed | April 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:18 p.m.