Triple
T515637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagoya High Court |
E10699
|
entity |
| Predicate | levelInCourtHierarchy |
P6053
|
FINISHED |
| Object | second 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: second instance | Statement: [Nagoya High Court, levelInCourtHierarchy, second instance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelInCourtHierarchy Context triple: [Nagoya High Court, levelInCourtHierarchy, second instance]
-
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.
createdLevelOfCourt
Indicates that an entity (such as a person, body, or law) is responsible for establishing or bringing into existence a particular level within a court system.
-
D.
highCourtSeat
Indicates that a location serves as the official seat or headquarters of a high court.
-
E.
hasLowerCourt
Indicates that one court functions as a subordinate or inferior court within the judicial hierarchy of another court.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f232fa688190b08a2fe3f22c7a6e |
completed | Feb. 28, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69a2f013c05481909e6dc87e7b20ebd8 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.