Triple
T2089264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taihoku |
E32628
|
entity |
| Predicate | romanization |
P2508
|
FINISHED |
| Object | Taihoku |
E32628
|
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: Taihoku | Statement: [Taihoku, romanization, Taihoku]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Taihoku Context triple: [Taihoku, romanization, Taihoku]
-
A.
Taihoku
chosen
Taihoku was the Japanese colonial-era name for Taipei, which served as the administrative and political center of Taiwan under Japanese rule.
-
B.
Tenjin
Tenjin is the Shinto kami of scholarship and learning, widely revered by students seeking academic success.
-
C.
Shimaore
Shimaore is a Bantu language closely related to Comorian, widely spoken by the local population of Mayotte in the Indian Ocean.
-
D.
Takamikura
Takamikura is the ornate imperial throne used in Kyoto for the enthronement ceremonies of Japanese emperors.
-
E.
Daitō
Daitō is a city in Osaka Prefecture, Japan, known as a residential and light industrial suburb within the Osaka metropolitan area.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba730a5c8190a85be72149574d79 |
completed | March 7, 2026, 5:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afce742d288190bfdcffb81c29a173 |
completed | March 10, 2026, 7:55 a.m. |
Created at: March 4, 2026, 7:43 p.m.