Triple
T3846666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Circuit Court in Shenyang |
E85186
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional branch of the Supreme People’s Court of China |
C12424
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: regional branch of the Supreme People’s Court of China Context triple: [Second Circuit Court in Shenyang, instanceOf, regional branch of the Supreme People’s Court of China]
-
A.
regional court
A regional court is a judicial body with authority to hear and decide legal cases within a specific geographic area below the national level.
-
B.
subdivision of the Supreme Court of Japan
A subdivision of the Supreme Court of Japan is an internal organizational unit, such as a petty bench or administrative division, that handles specific categories of judicial or administrative functions within the Court.
-
C.
branch court
A branch court is a subsidiary judicial facility or division located away from a main courthouse to provide more accessible legal services within a specific geographic area.
-
D.
regional administrative branch
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
-
E.
high court branch
chosen
A high court branch is a regional division or bench of a higher judiciary that exercises the court’s jurisdiction over a specific geographic area, hearing appeals and significant legal matters within that territory.
- F. None of above.
Provenance (1 batch)
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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.