Triple
T8977880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiaki Homma |
E214440
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Homma |
E214440
|
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: Homma | Statement: [Chiaki Homma, familyName, Homma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Homma Context triple: [Chiaki Homma, familyName, Homma]
-
A.
Homma
chosen
Homma is a Japanese surname borne by various notable individuals across fields such as the military, arts, and sports.
-
B.
Sannomiya
Sannomiya is a major commercial and transportation hub in central Kobe, Japan, known for its shopping streets, nightlife, and role as the city’s downtown core.
-
C.
Kamiyama
Kamiyama is a Japanese surname borne by various individuals, including artists, athletes, and public figures.
-
D.
Miyazya
Miyazya is one of the spring months in the Ethiopian calendar, roughly corresponding to April in the Gregorian calendar.
-
E.
Fujinomiya
Fujinomiya is a city in Shizuoka Prefecture, Japan, known as a major gateway to Mount Fuji and for its scenic views of the iconic volcano.
- 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_69ca839ea8b88190922c6a326ffcc0d3 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67a33c8481909125acf4b7f0a919 |
completed | April 1, 2026, 12:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d02fb3a27081909bc8504c92d8942f |
completed | April 3, 2026, 9:22 p.m. |
Created at: March 30, 2026, 7:02 p.m.