Triple
T3568633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomonaga Haruhiko |
E75513
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Tomonaga |
E75513
|
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: Tomonaga | Statement: [Tomonaga Haruhiko, familyName, Tomonaga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tomonaga Context triple: [Tomonaga Haruhiko, familyName, Tomonaga]
-
A.
Tomonaga
chosen
Tomonaga is a Japanese surname most notably borne by Sin-Itiro Tomonaga, a Nobel Prize–winning theoretical physicist known for his contributions to quantum electrodynamics.
-
B.
Tomoyuki
Tomoyuki is a Japanese masculine given name borne by various notable figures in fields such as the military, arts, and entertainment.
-
C.
Takaichi
Takaichi is a Japanese surname most prominently associated with conservative politician Sanae Takaichi.
-
D.
Tamada
Tamada is the traditional Georgian toastmaster who leads feasts and orchestrates toasts during the supra, Georgia’s ceremonial banquet.
-
E.
Takanami
Takanami was a Japanese destroyer of the Imperial Japanese Navy during World War II, notable for being sunk in the Battle of Tassafaronga in 1942.
- 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_69ad85d512708190829c8b2d3a2ccfb8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0c083ac8190a71cd9ede2114cac |
completed | March 8, 2026, 6:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b402ebfd548190a155fb1e65aefa8d |
completed | March 13, 2026, 12:28 p.m. |
Created at: March 8, 2026, 3:21 p.m.