Triple

T18199058
Position Surface form Disambiguated ID Type / Status
Subject Gosei E435733 entity
Predicate hasRelatedTerm P37 FINISHED
Object Rokusei 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: Rokusei | Statement: [Gosei, hasRelatedTerm, Rokusei]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rokusei
Context triple: [Gosei, hasRelatedTerm, Rokusei]
  • A. Rokusei chosen
    Rokusei is a Japanese tokusatsu superhero team that succeeds Gosei in the narrative sequence of its series.
  • B. Ryojun
    Ryojun is the former Japanese name for Lüshunkou, a strategically important port city in northeastern China historically known for its military significance.
  • C. Shōryaku
    Shōryaku was a Japanese era name (nengō) of the late 10th century, used during the reign of Emperor Shirakawa.
  • D. Tsubami
    Tsubami is one of the official bird mascots of the Tokyo Yakult Swallows baseball team, known for her cute design and energetic support of the club.
  • E. Ryujo
    Ryujo was a light aircraft carrier of the Imperial Japanese Navy that served in the early stages of World War II before being sunk in the Battle of the Eastern Solomons in 1942.
  • 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_69d8b90dba6481908e119eb9aa4ca0cb completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e0d545f4819090285d1446bd3c27 completed April 19, 2026, 2:04 p.m.
Created at: April 10, 2026, 10:31 a.m.