Triple
T29100663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yakuza |
E736632
|
entity |
| Predicate | KamurochoBasedOn |
P166323
|
FINISHED |
| Object | Kabukicho, Tokyo |
—
|
NE NERFINISHED |
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: Kabukicho, Tokyo | Statement: [Yakuza, KamurochoBasedOn, Kabukicho, Tokyo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: KamurochoBasedOn Context triple: [Yakuza, KamurochoBasedOn, Kabukicho, Tokyo]
-
A.
ichinomiya
Indicates a relationship where a location or institution holds the status of "Ichinomiya," the primary or highest-ranking Shinto shrine of a historical province.
-
B.
OkamaLocation
Indicates that a location is associated with or designated for okama (cross-dressing or gender-nonconforming) individuals or culture.
-
C.
JapaneseMission
Indicates a mission, delegation, or official undertaking that is specifically associated with Japan or originates from Japanese authorities or organizations.
-
D.
TenjinMatsuriLocation
Indicates the location where the Tenjin Matsuri festival takes place or is held.
-
E.
shrineCity
Indicates that a city is the location of, or is associated with, a particular shrine.
- F. None of above. chosen
Provenance (4 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 11:11 a.m.