Triple
T36915474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 高輪 |
E913034
|
entity |
| Predicate | belongsToWardNumberingSystem |
P92342
|
FINISHED |
| Object | Minato ward district system |
—
|
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: Minato ward district system | Statement: [高輪, belongsToWardNumberingSystem, Minato ward district system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToWardNumberingSystem Context triple: [高輪, belongsToWardNumberingSystem, Minato ward district system]
-
A.
isWardOf
Indicates that one entity is under the guardianship, protection, or legal care of another entity as their ward.
-
B.
locatedInCityWard
Indicates that one entity is situated within the administrative boundaries of a specific city ward.
-
C.
municipalWardType
Indicates the specific category or classification of a municipal ward within a local government or administrative structure.
-
D.
numberingSystemBasedOn
chosen
Indicates that one numbering system is derived from, structured according to, or conceptually dependent on another numbering system.
-
E.
hasNeighbouringWard
Indicates that one ward is directly adjacent to or borders another ward geographically.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffff262fac8190a26ed0577e1860bd |
completed | May 10, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69fffcad7d7c8190a4ad7bb35e33bb75 |
completed | May 10, 2026, 3:34 a.m. |
Created at: May 3, 2026, 4:13 p.m.