Triple
T8061496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wako |
E188130
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Asaka |
E232613
|
NE 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: Asaka | Statement: [Wako, borderedBy, Asaka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Asaka Context triple: [Wako, borderedBy, Asaka]
-
A.
Asaka
chosen
Asaka is a Japanese noble family name historically associated with a collateral branch of the Imperial Family, including Prince Asaka Yasuhiko.
-
B.
Hisako
Hisako is a member of the Japanese imperial family known as Princess Takamado, recognized for her cultural, charitable, and international goodwill activities.
-
C.
Tsutako
Tsutako is a Japanese given name, most notably borne by Tsutako Nakasone.
-
D.
Sakae
Sakae is a major downtown commercial and entertainment district in Nagoya, Japan, known for its shopping, nightlife, and landmark attractions.
-
E.
Yamanakako
Yamanakako is a village in Yamanashi Prefecture, Japan, known for Lake Yamanaka, one of the Fuji Five Lakes located near Mount Fuji.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82b2f68881908c50560697e210da |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fcc61c0819085edc26e75c5f6d5 |
completed | March 31, 2026, 3:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf278d5abc8190a9330918486e464f |
completed | April 3, 2026, 2:35 a.m. |
Created at: March 30, 2026, 5:26 p.m.