Triple
T11515793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamato clan |
E273026
|
entity |
| Predicate | usedTitle |
P3254
|
FINISHED |
| Object | Ōkimi |
E281665
|
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: Ōkimi | Statement: [Yamato clan, usedTitle, Ōkimi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ōkimi Context triple: [Yamato clan, usedTitle, Ōkimi]
-
A.
Ōkimi
chosen
Ōkimi was the title used for the supreme ruler of early Japan’s Yamato state, a precursor to the later Japanese emperor.
-
B.
Oghi
Oghi is a town in Pakistan's Khyber Pakhtunkhwa province, known as a local administrative and commercial center within the Hazara region.
-
C.
Otomari
Otomari was a settlement in southern Sakhalin (then Karafuto) that served as a strategic Japanese military garrison area before and during World War II.
-
D.
Okimi
Okimi was a former town in Hiroshima Prefecture, Japan, that later became part of the city of Etajima through a municipal merger.
-
E.
Ōjin
Ōjin is a semi-legendary early Japanese emperor traditionally regarded as the 15th ruler of Japan and later venerated as the Shinto war deity Hachiman.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d87fcc72a48190b81acedfcc8685d3 |
completed | April 10, 2026, 4:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e625143a608190a1119b30c08df0fd |
completed | April 20, 2026, 1:07 p.m. |
Created at: April 8, 2026, 9:36 p.m.