Triple
T14324878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kabuki-za Theatre |
E355189
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | 歌舞伎座 |
E355189
|
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: 歌舞伎座 | Statement: [Kabuki-za Theatre, nativeName, 歌舞伎座]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 歌舞伎座 Context triple: [Kabuki-za Theatre, nativeName, 歌舞伎座]
-
A.
歌舞伎町
歌舞伎町 is Tokyo’s most famous entertainment and red-light district, known for its dense concentration of bars, restaurants, nightclubs, and neon-lit nightlife.
-
B.
国立文楽劇場
国立文楽劇場は、日本の伝統芸能である文楽を中心に上演するため大阪に設けられた国立の専門劇場です。
-
C.
Kabuki-za Theatre
chosen
Kabuki-za Theatre is Tokyo’s principal and most famous kabuki playhouse, renowned for its traditional performances and historic architecture.
-
D.
Takatsuki Arts Theatre
Takatsuki Arts Theatre is a cultural and performing arts venue in Takatsuki, Japan, hosting concerts, theatrical productions, and community arts events.
-
E.
Shinjuku Koma Theater
Shinjuku Koma Theater was a famous large-scale entertainment venue in Tokyo’s Shinjuku district, known for hosting popular music, theater, and live performances until its closure and demolition in the late 2000s.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de883e6a288190b6c22f630a1eef3c |
completed | April 14, 2026, 6:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4690a79c819099cc4ae9a10ba0db |
completed | May 8, 2026, 2:12 a.m. |
Created at: April 10, 2026, 1:13 a.m.