Triple

T15716192
Position Surface form Disambiguated ID Type / Status
Subject Aoba-class cruiser E380965 entity
Predicate originOfName P453 FINISHED
Object Mount Aoba 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: Mount Aoba | Statement: [Aoba-class cruiser, originOfName, Mount Aoba]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mount Aoba
Context triple: [Aoba-class cruiser, originOfName, Mount Aoba]
  • A. Mount Aoba chosen
    Mount Aoba is a Japanese volcano whose name has been used for various ships and locations, reflecting its cultural and geographical significance in Japan.
  • B. Mount Rokko
    Mount Rokko is a prominent mountain range near Kobe, Japan, known for its panoramic night views, hiking trails, and recreational facilities.
  • C. Mount Furutaka
    Mount Furutaka is a mountain in Japan notable enough to have lent its name to the Imperial Japanese Navy cruiser Furutaka.
  • D. Mount Ōmine
    Mount Ōmine is a sacred mountain in Japan’s Nara Prefecture, renowned as a major center of Shugendō mountain asceticism and a UNESCO World Heritage pilgrimage site.
  • E. Mount Otokoyama
    Mount Otokoyama is a low, wooded hill in Yawata, Kyoto Prefecture, known as a sacred site and scenic viewpoint overlooking the Yodo River area.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d86d9bf930819082b30cf6d169297c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e04f91beb08190bd91bf9306737c3b completed April 16, 2026, 2:55 a.m.
Created at: April 10, 2026, 4:45 a.m.