Triple

T13482551
Position Surface form Disambiguated ID Type / Status
Subject To no Chujo E318406 entity
Predicate hasSibling P363 FINISHED
Object Aoi no Ue E318404 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: Aoi no Ue | Statement: [To no Chujo, hasSibling, Aoi no Ue]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aoi no Ue
Context triple: [To no Chujo, hasSibling, Aoi no Ue]
  • A. Aoi no Ue chosen
    Aoi no Ue is a noblewoman and the first principal wife of Prince Genji in the classic Japanese literary work "The Tale of Genji."
  • B. Aishō
    Aishō is a town in Shiga Prefecture, Japan, known for its rural character and historical sites.
  • C. Hikari no Wa
    Hikari no Wa is a Japanese new religious movement that emerged from the remnants of Aum Shinrikyo, promoting a reformed, non-violent spiritual path.
  • D. Hieda no Are
    Hieda no Are was a Japanese court reciter traditionally credited with memorizing the oral histories that formed the basis of the early 8th-century chronicle Kojiki.
  • E. Koi no omoni
    Koi no omoni is a classical Noh play by Zeami Motokiyo that explores themes of love, longing, and emotional burden through highly stylized performance and poetic language.
  • 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_69d806b6bfec819089222715b2e86c8e completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaf3868ec8190a6a1803018d4f2d8 completed April 12, 2026, 2:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69f78ad8903c8190afbf15234a81d657 completed May 3, 2026, 5:50 p.m.
Created at: April 9, 2026, 9:42 p.m.