Triple

T20191496
Position Surface form Disambiguated ID Type / Status
Subject Bulborb E492987 entity
Predicate hasVariant P455 FINISHED
Object Hairy Bulborb 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: Hairy Bulborb | Statement: [Bulborb, hasVariant, Hairy Bulborb]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hairy Bulborb
Context triple: [Bulborb, hasVariant, Hairy Bulborb]
  • A. Bulborb chosen
    Bulborb is a large, frog-like, spotted predator from the Pikmin video game series known for devouring Pikmin in a single bite.
  • B. Blooper
    Blooper is a recurring squid-like enemy from the Super Mario video game series, typically found underwater and known for its erratic swimming patterns.
  • C. Blooper
    Blooper is the fuzzy, energetic costumed mascot of Major League Baseball’s Atlanta Braves, known for entertaining fans with comedic antics at games.
  • D. Sigmund Ooze
    Sigmund Ooze is the friendly young sea monster who serves as the central character in the 1970s children's television series "Sigmund and the Sea Monsters."
  • E. Labynkyr monster
    The Labynkyr monster is a cryptid said to inhabit Russia’s remote Lake Labynkyr, often described in local legends as a large, mysterious lake creature akin to the Loch Ness Monster.
  • 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_69da6268a034819081cbd9ea5a1c9475 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66ad593f88190a1e534fed38b3cd7 completed April 20, 2026, 6:05 p.m.
Created at: April 11, 2026, 11:37 p.m.