Triple
T5808752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kao Hsiao-yuan |
E128813
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Kao |
E128813
|
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: Kao | Statement: [Kao Hsiao-yuan, familyName, Kao]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kao Context triple: [Kao Hsiao-yuan, familyName, Kao]
-
A.
Kao
chosen
Kao is a Chinese surname borne by numerous individuals, including notable figures in science, business, and the arts.
-
B.
Michishio
Michishio was a Japanese Navy destroyer that served in World War II and was sunk during the Battle of Surigao Strait in 1944.
-
C.
Kiesen
Kiesen is a municipality in the canton of Bern, Switzerland, served by a station on the Bern–Thun railway line.
-
D.
Kido
Kido is a Japanese surname most famously borne by Kido Takayoshi, a key samurai statesman of the Meiji Restoration.
-
E.
Mibuchi
Mibuchi is a Japanese surname borne by individuals such as Tadahiko Mibuchi.
- 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1867a481909a7ea3331dbb04ce |
completed | March 22, 2026, 5:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0bfb903788190bae497fe72bd1e78 |
completed | March 23, 2026, 4:21 a.m. |
Created at: March 22, 2026, 3:52 p.m.