Triple

T11563872
Position Surface form Disambiguated ID Type / Status
Subject Coco Bandicoot E274205 entity
Predicate enemy P4567 FINISHED
Object Doctor N. Gin E931042 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: Doctor N. Gin | Statement: [Coco Bandicoot, enemy, Doctor N. Gin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Doctor N. Gin
Context triple: [Coco Bandicoot, enemy, Doctor N. Gin]
  • A. Doctor N. Gin chosen
    Doctor N. Gin is a deranged, rocket-headed scientist and weapons expert who serves as one of the primary villainous henchmen in the Crash Bandicoot video game series.
  • B. Dr. N. Gin
    Dr. N. Gin is a recurring mad scientist villain in the Crash Bandicoot video game series, known for the missile lodged in his head and his role as one of Doctor Neo Cortex’s chief henchmen.
  • C. Goro
    Goro is a four-armed Shokan prince and powerful sub-boss character from the Mortal Kombat fighting game series.
  • D. Goro
    Goro is a town located in the Bale Zone of the Oromia Region in southeastern Ethiopia.
  • E. Dr. Julius No
    Dr. Julius No is a fictional criminal mastermind and the titular villain of Ian Fleming’s James Bond novel and its 1962 film adaptation, known for his metal hands and plot to disrupt American missile tests.
  • 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_69d6aae5ac3c81908d2b0a3a665665b2 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d88dd321f88190a57ecaf079fbbc3f completed April 10, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69e6e89e73b481908175576f4ec8d39a completed April 21, 2026, 3:01 a.m.
Created at: April 8, 2026, 9:37 p.m.