Triple
T28093934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tobata-ku |
E710033
|
entity |
| Predicate | belongsToNationalJurisdiction |
P7728
|
FINISHED |
| Object | Japan |
—
|
NE NERFINISHED |
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: Japan | Statement: [Tobata-ku, belongsToNationalJurisdiction, Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToNationalJurisdiction Context triple: [Tobata-ku, belongsToNationalJurisdiction, Japan]
-
A.
countryOfJurisdiction
chosen
Indicates the country whose legal authority or jurisdiction governs or applies to a given entity, action, or arrangement.
-
B.
territorialJurisdictionIncludes
Indicates that one authority’s territorial jurisdiction encompasses or extends over a specified geographic area or location.
-
C.
associatedWithJurisdiction
Indicates that an entity has a formal or relevant connection to a particular legal or administrative jurisdiction.
-
D.
usesJurisdiction
Indicates that one entity applies or operates under the legal authority or rules of a particular jurisdiction.
-
E.
definedJurisdictionOf
Indicates that one entity formally establishes or specifies the scope, boundaries, or authority of another entity’s jurisdiction.
- 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_69ef9b70fd108190a875953b2e50ca91 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 27, 2026, 9 p.m.