Triple

T19165915
Position Surface form Disambiguated ID Type / Status
Subject Teodor Axentowicz E469179 entity
Predicate givenName P17 FINISHED
Object Teodor 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: Teodor | Statement: [Teodor Axentowicz, givenName, Teodor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Teodor
Context triple: [Teodor Axentowicz, givenName, Teodor]
  • A. Teodor chosen
    Teodor is a given name, commonly used in various European languages, that corresponds to the English name Theodore.
  • B. Theodor
    Theodor "Ted" Nelson is an American pioneer of information technology best known for coining the term "hypertext" and envisioning global hyperlinked document systems.
  • C. Theodor
    Theodor is the given name of Emil Theodor Kocher, a Swiss surgeon and Nobel laureate renowned for his pioneering work in thyroid surgery.
  • D. Theodor
    Theodor is a masculine given name of Greek origin, commonly used in various European languages and meaning “gift of God.”
  • E. Theodor
    Theodor is a given name most notably associated with Austrian-American actor, folk singer, and activist Theodore Bikel.
  • 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_69d8dd09d5a081909ae43c286651ae5a completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5f15ee064819087f9fd822236298f completed April 20, 2026, 9:26 a.m.
Created at: April 10, 2026, 12:06 p.m.