Triple

T15877960
Position Surface form Disambiguated ID Type / Status
Subject King Koopa E384997 entity
Predicate parentOf P120 FINISHED
Object Bowser Jr. E377127 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: Bowser Jr. | Statement: [King Koopa, parentOf, Bowser Jr.]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bowser Jr.
Context triple: [King Koopa, parentOf, Bowser Jr.]
  • A. Bowser Jr. chosen
    Bowser Jr. is a recurring antagonist in the Super Mario series, known as Bowser’s mischievous son who frequently schemes against Mario and his allies.
  • B. Bowser
    Bowser is the iconic fire-breathing, turtle-like villain from Nintendo’s Super Mario series, known as Mario’s arch-nemesis and the king of the Koopas.
  • C. Bowser
    Bowser is a small unincorporated coastal community on central Vancouver Island in British Columbia, Canada.
  • D. Morton Koopa Jr.
    Morton Koopa Jr. is one of the Koopalings in the Super Mario series, a recurring boss character who serves as a high-ranking minion of Bowser.
  • E. Koopa Troopa
    Koopa Troopa is a turtle-like enemy species from Nintendo’s Mario series, known for retreating into its shell when jumped on and often serving as a basic, recurring foe throughout the games.
  • 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_69d86da4e86481909f1325fdc971b5ec completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e155fec9d4819081efea504e1e3952 completed April 16, 2026, 9:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffcf1045f88190ae96a2477497038c completed May 10, 2026, 12:19 a.m.
Created at: April 10, 2026, 4:51 a.m.