Triple
T541703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sendai High Court |
E12643
|
entity |
| Predicate | courtHierarchyLevel |
P6053
|
FINISHED |
| Object | intermediate appellate 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: intermediate appellate court | Statement: [Sendai High Court, courtHierarchyLevel, intermediate appellate court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtHierarchyLevel Context triple: [Sendai High Court, courtHierarchyLevel, intermediate appellate court]
-
A.
jurisdictionLevel
Indicates the scope or tier of authority under which an entity or action is legally governed or regulated.
-
B.
legalHierarchyRank
chosen
Indicates the relative position or level of authority an entity holds within a legal or judicial hierarchy.
-
C.
highCourtSeat
Indicates that a location serves as the official seat or headquarters of a high court.
-
D.
judicialCircuit
Indicates the judicial circuit within which a legal entity, case, or jurisdiction is organized or falls under authority.
-
E.
highestCourtOf
Indicates that one entity is the supreme judicial authority or top-level court within the jurisdiction or legal system of another entity.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49861195081909540eaf402a5401a |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b8098481908097228db8ad0262 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.