Triple
T14079405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oita District Court |
E338824
|
entity |
| Predicate | courtSystemTier |
P6712
|
FINISHED |
| Object | second tier below high courts in Japan |
—
|
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: second tier below high courts in Japan | Statement: [Oita District Court, courtSystemTier, second tier below high courts in Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtSystemTier Context triple: [Oita District Court, courtSystemTier, second tier below high courts in Japan]
-
A.
courtRank
Indicates the formal hierarchical rank or status an individual holds within a court or courtly system.
-
B.
courtSystemSegment
Indicates a specific division or segment within a broader court system to which a legal matter, case, or entity is assigned or associated.
-
C.
jurisdictionLevel
chosen
Indicates the scope or tier of authority under which an entity or action is legally governed or regulated.
-
D.
hadCourtLevel
Indicates the specific hierarchical level of the court at which a legal case or judicial action took place.
-
E.
judicialCircuit
Indicates the judicial circuit within which a legal entity, case, or jurisdiction is organized or falls under authority.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5c5e027881908f610f5bab7598d4 |
completed | April 14, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.