Triple
T10549263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohira Chikako |
E248901
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Ōhira |
E346815
|
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: Ōhira | Statement: [Ohira Chikako, familyName, Ōhira]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ōhira Context triple: [Ohira Chikako, familyName, Ōhira]
-
A.
Ōhira
chosen
Ōhira is a Japanese surname most notably associated with Masayoshi Ōhira, a former Prime Minister of Japan.
-
B.
Takahira
Takahira was the personal name of Emperor Go-Toba, a late 12th- to early 13th-century Japanese emperor known for his political struggles with the shogunate and his patronage of the arts.
-
C.
Hiranaka
Hiranaka is a Japanese surname borne by individuals such as former professional boxer Akinobu Hiranaka.
-
D.
Takaishi
Takaishi is a city in Osaka Prefecture, Japan, known as a small industrial and residential hub within the Osaka metropolitan area.
-
E.
Ozaki
Ozaki is a Japanese surname borne by various notable figures in politics, literature, and the arts.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d526d3e45c819099b360f9cfd3dd50 |
completed | April 7, 2026, 3:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7304bc684819083ca999f283b0cb3 |
completed | May 3, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:33 p.m.