Triple
T14032317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagasaki District Court |
E337620
|
entity |
| Predicate | judicialTier |
P71353
|
FINISHED |
| Object | first instance |
—
|
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: first instance | Statement: [Nagasaki District Court, judicialTier, first instance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judicialTier Context triple: [Nagasaki District Court, judicialTier, first instance]
-
A.
jurisdictionLevel
Indicates the scope or tier of authority under which an entity or action is legally governed or regulated.
-
B.
hadCourtLevel
chosen
Indicates the specific hierarchical level of the court at which a legal case or judicial action took place.
-
C.
courtRank
Indicates the formal hierarchical rank or status an individual holds within a court or courtly system.
-
D.
judicialBody
Indicates that an entity serves as a court or tribunal with authority to adjudicate legal disputes or interpret and apply the law.
-
E.
typeOfJurisdiction
Indicates the specific kind or category of legal authority or control that one jurisdiction holds in relation to a given legal or administrative context.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fab17008190981f1808726fa11c |
completed | April 14, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.