Triple
T2311806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sup Ct |
E51974
|
entity |
| Predicate | courtLevelReferredTo |
P9881
|
FINISHED |
| Object | trial-level court |
—
|
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: trial-level court | Statement: [Sup Ct, courtLevelReferredTo, trial-level court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtLevelReferredTo Context triple: [Sup Ct, courtLevelReferredTo, trial-level court]
-
A.
higherCourtOf
Indicates that one court has legal authority to review, overrule, or supervise the decisions and actions of another, lower court in the judicial hierarchy.
-
B.
affectedCourt
Indicates that a particular court is impacted or influenced by a specified action, decision, or legal matter.
-
C.
trialCourt
chosen
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).
-
D.
hasLowerCourt
Indicates that one court functions as a subordinate or inferior court within the judicial hierarchy of another court.
-
E.
jurisdictionLevel
Indicates the scope or tier of authority under which an entity or action is legally governed or regulated.
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.