Triple

T17059885
Position Surface form Disambiguated ID Type / Status
Subject Krakus Mound E413927 entity
Predicate namedAfter P63 FINISHED
Object King Krakus E1173378 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: King Krakus | Statement: [Krakus Mound, namedAfter, King Krakus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: King Krakus
Context triple: [Krakus Mound, namedAfter, King Krakus]
  • A. King Krakus chosen
    King Krakus is a legendary ruler of Kraków in Polish folklore, famed for slaying the Wawel Dragon and founding the city.
  • B. Gundoald
    Gundoald was a member of the early medieval Bavarian nobility, associated with the ruling dynasty that governed parts of what is now southern Germany.
  • C. Gundemar
    Gundemar was a 7th-century Visigothic king of Hispania and Septimania who ruled briefly before being succeeded by Sisebut.
  • D. Thankmar
    Thankmar was a 10th-century German nobleman and the eldest son of King Henry the Fowler, whose disputed legitimacy led to his rebellion against his half-brother Otto I.
  • E. Guiderius
    Guiderius is a noble prince and one of the central heroic figures in William Shakespeare’s play "Cymbeline," known for his bravery and hidden royal identity.
  • 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_69d886cde3d481908d4d01ba88ba7eb7 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3db7c21a881909bfb67080706612f completed April 18, 2026, 7:29 p.m.
NED1 Entity disambiguation (via context triple) batch_6a012349b2c88190a5c5e06a5cae1ac5 completed May 11, 2026, 12:31 a.m.
Created at: April 10, 2026, 5:34 a.m.