Triple
T9309080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cutter |
E223962
|
entity |
| Predicate | caseCourtLevel |
P71353
|
FINISHED |
| Object | federal |
—
|
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: federal | Statement: [Cutter, caseCourtLevel, federal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseCourtLevel Context triple: [Cutter, caseCourtLevel, federal]
-
A.
hadCourtLevel
chosen
Indicates the specific hierarchical level of the court at which a legal case or judicial action took place.
-
B.
trialCourt
Indicates that a legal matter, decision, or proceeding is associated with, handled by, or occurring in a court of first instance (the trial-level court).
-
C.
jurisdictionLevel
Indicates the scope or tier of authority under which an entity or action is legally governed or regulated.
-
D.
highestTrialCourtOf
Indicates that one entity serves as the supreme or final-level trial court within the judicial hierarchy of another entity (such as a jurisdiction or legal system).
-
E.
courtRank
Indicates the formal hierarchical rank or status an individual holds within a court or courtly system.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd1daba67c819081d53545d67ef127 |
completed | April 1, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.