Triple

T6236841
Position Surface form Disambiguated ID Type / Status
Subject central Tokyo E139497 entity
Predicate contains P35 FINISHED
Object Aoyama E190766 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: Aoyama | Statement: [central Tokyo, contains, Aoyama]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aoyama
Context triple: [central Tokyo, contains, Aoyama]
  • A. Aoyama chosen
    Aoyama is an upscale district in Tokyo known for its high-end fashion boutiques, modern architecture, and trendy cafes and galleries.
  • B. Ōyama
    Ōyama is a Japanese surname borne by various notable figures in Japan’s military, political, and cultural history.
  • C. Yoiyama
    Yoiyama is the lively evening street festival held before the main Gion Matsuri parade in Kyoto, featuring illuminated festival floats, food stalls, and traditional music.
  • D. Sasayama
    Sasayama is a historic castle town in Hyōgo Prefecture, Japan, known for its well-preserved Edo-period streets, Sasayama Castle ruins, and traditional local cuisine.
  • E. Arakawa
    Arakawa is a special ward in Tokyo, Japan, known for its mix of traditional residential neighborhoods and industrial areas along the Arakawa River.
  • 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_69c008b0e7ac8190808a59573ee646f3 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c063021258819093a9237041816638 completed March 22, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69c71a5979208190b3bedb6234181245 completed March 28, 2026, 12:01 a.m.
Created at: March 22, 2026, 4:23 p.m.