Triple

T18769227
Position Surface form Disambiguated ID Type / Status
Subject Eastern Hungarian Kingdom E458970 entity
Predicate capital P234 FINISHED
Object Lippa 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: Lippa | Statement: [Eastern Hungarian Kingdom, capital, Lippa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lippa
Context triple: [Eastern Hungarian Kingdom, capital, Lippa]
  • A. Lippa chosen
    Lippa is a historical town that served as one of the residences of Polish princess and Hungarian queen Isabella Jagiellon.
  • B. Leppe
    Leppe is a small river in western Germany that flows through the hilly Bergisches Land region of North Rhine-Westphalia.
  • C. Libo
    Libo is an ancient Roman cognomen associated with members of the patrician Julii family.
  • D. Leipoa
    Leipoa is a bird genus in the megapode family best known for including the Australian malleefowl, a ground-dwelling species that incubates its eggs in large mounds of decomposing vegetation.
  • E. Liluah
    Liluah is a suburban locality in the Howrah district of West Bengal, India, known for its residential areas and railway facilities near Kolkata.
  • 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_69d8d395dba0819087568404508590cb completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e58d867264819098ae35c9feab3bb4 completed April 20, 2026, 2:20 a.m.
Created at: April 10, 2026, 11:52 a.m.