Triple
T16206740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanmu |
E393347
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Yamabe |
E394943
|
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: Yamabe | Statement: [Kanmu, givenName, Yamabe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yamabe Context triple: [Kanmu, givenName, Yamabe]
-
A.
Yamabe
chosen
Yamabe was the personal name of Emperor Kanmu, a powerful Japanese emperor of the late 8th and early 9th centuries who moved the capital to Heian-kyō (Kyoto).
-
B.
Yasu
Yasu is a Japanese city located in Shiga Prefecture, known for its blend of residential areas, local industry, and proximity to Lake Biwa.
-
C.
Yorinaga
Yorinaga is a Japanese given name most notably borne by the Heian-period court noble Fujiwara no Yorinaga.
-
D.
Takayoshi
Takayoshi is a Japanese given name notably borne by Kido Takayoshi, a key samurai and statesman of the Meiji Restoration.
-
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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227101a3c819095ef40e50bf66433 |
completed | April 17, 2026, 12:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00078fa2ac8190a0a2cf38bc41498d |
completed | May 10, 2026, 4:20 a.m. |
Created at: April 10, 2026, 5:03 a.m.