Triple

T18584704
Position Surface form Disambiguated ID Type / Status
Subject Iori Yagami E454204 entity
Predicate enemy P4567 FINISHED
Object Orochi 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: Orochi | Statement: [Iori Yagami, enemy, Orochi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Orochi
Context triple: [Iori Yagami, enemy, Orochi]
  • A. Yamata no Orochi chosen
    Yamata no Orochi is a legendary eight-headed, eight-tailed serpent-dragon from Japanese mythology, famed as a fearsome monster slain by the storm god Susanoo.
  • B. Garuga
    Garuga is a small genus of tropical trees in the frankincense and myrrh family Burseraceae, known for its resinous bark and occurrence in Asian and Pacific regions.
  • C. Hebi
    Hebi is a prefecture-level city in northern Henan Province, China, known for its coal resources and developing industrial base.
  • D. Tuda-Mengu
    Tuda-Mengu was a 13th-century Mongol ruler who briefly led the Golden Horde during a period of internal strife and shifting alliances within the Mongol Empire.
  • E. Jiryaku
    Jiryaku was a Japanese era name (nengō) of the late Heian period, used during the reign of Emperor Go-Sanjō.
  • 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_69d8d38ae7e081908a98df1251842402 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e545b0dff08190a3be481faec34a3c completed April 19, 2026, 9:14 p.m.
Created at: April 10, 2026, 11:44 a.m.