Triple
T16079421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanda River |
E390064
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Kanda-gawa |
E577501
|
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: Kanda-gawa | Statement: [Kanda River, alsoKnownAs, Kanda-gawa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kanda-gawa Context triple: [Kanda River, alsoKnownAs, Kanda-gawa]
-
A.
Kanda
chosen
Kanda is a historic commercial and educational district in central Tokyo known for its bookstores, universities, and traditional shrines.
-
B.
Eikandō
Eikandō is a historic Buddhist temple in Kyoto, Japan, renowned for its autumn foliage and iconic statue of the Amida Buddha looking over its shoulder.
-
C.
Kuwana
Kuwana is a city in central Japan known historically as a post town on the Tōkaidō route and for its cultural sites and traditional festivals.
-
D.
Kan’onji
Kan’onji is a coastal city in western Kagawa Prefecture on Japan’s Shikoku Island, known for its historic temples and scenic views of the Seto Inland Sea.
-
E.
Takamikura
Takamikura is the ornate imperial throne used in Kyoto for the enthronement ceremonies of Japanese emperors.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e18448bebc8190b0e84b1da097bf8b |
completed | April 17, 2026, 12:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00c790ec64819084277c156f38a7de |
completed | May 10, 2026, 5:59 p.m. |
Created at: April 10, 2026, 4:57 a.m.