Triple

T20331799
Position Surface form Disambiguated ID Type / Status
Subject Maki Horikita E492500 entity
Predicate givenName P17 FINISHED
Object Maki 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: Maki | Statement: [Maki Horikita, givenName, Maki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maki
Context triple: [Maki Horikita, givenName, Maki]
  • A. Maki chosen
    Maki is a Japanese surname most notably associated with Fumihiko Maki, a prominent modernist architect known for his innovative urban and architectural designs.
  • B. Maki
    Maki is an Israeli communist political party historically associated with figures such as Meir Vilner and the broader leftist movement in Israel.
  • C. Miyazu
    Miyazu is a coastal city in northern Kyoto Prefecture, Japan, best known as the gateway to the scenic sandbar Amanohashidate, one of Japan’s traditional “Three Views.”
  • D. Komaki
    Komaki is a city in Aichi Prefecture, Japan, known for its historical sites, including Komaki Castle, and its role as part of the Nagoya metropolitan area.
  • E. Yamanakako
    Yamanakako is a village in Yamanashi Prefecture, Japan, known for Lake Yamanaka, one of the Fuji Five Lakes located near Mount Fuji.
  • 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_69e0b4a1a09881908d97270d6971a25a completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e677e7baf481909282293d78597634 completed April 20, 2026, 7 p.m.
Created at: April 16, 2026, 11:22 a.m.