Triple

T1762113
Position Surface form Disambiguated ID Type / Status
Subject Leopold III of Belgium E38679 entity
Predicate givenName P17 FINISHED
Object Leopold E110183 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: Leopold | Statement: [Leopold III of Belgium, givenName, Leopold]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leopold
Context triple: [Leopold III of Belgium, givenName, Leopold]
  • A. Leopold chosen
    Leopold is a masculine given name of Germanic origin historically borne by various European rulers, saints, and notable figures.
  • B. Ernst
    Ernst is a masculine given name of Germanic origin, commonly used in German-speaking and Scandinavian countries.
  • C. Günther
    Günther is a German masculine given name traditionally associated with figures of Germanic origin and culture.
  • D. Theodor
    Theodor "Ted" Nelson is an American pioneer of information technology best known for coining the term "hypertext" and envisioning global hyperlinked document systems.
  • E. Theodor
    Theodor is the given name of Emil Theodor Kocher, a Swiss surgeon and Nobel laureate renowned for his pioneering work in thyroid surgery.
  • 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_69a8862d562481908d7025a1c1f67c0d completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa6463ac0081909e9ebe6ebf1db857 completed March 6, 2026, 5:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69add1b679d88190b3c6e50c96f917e4 completed March 8, 2026, 7:44 p.m.
Created at: March 4, 2026, 7:31 p.m.