Triple
T21361034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Theodor of Bavaria |
E526777
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Theodor |
—
|
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: Theodor | Statement: [Prince Theodor of Bavaria, givenName, Theodor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Theodor Context triple: [Prince Theodor of Bavaria, givenName, Theodor]
-
A.
Theodor
Theodor "Ted" Nelson is an American pioneer of information technology best known for coining the term "hypertext" and envisioning global hyperlinked document systems.
-
B.
Theodor
Theodor is the given name of Emil Theodor Kocher, a Swiss surgeon and Nobel laureate renowned for his pioneering work in thyroid surgery.
-
C.
Theodor
Theodor is a given name most notably associated with Austrian-American actor, folk singer, and activist Theodore Bikel.
-
D.
Theodor
chosen
Theodor is a masculine given name of Greek origin, commonly used in various European languages and meaning “gift of God.”
-
E.
Theodor-Peter
Theodor-Peter, better known as Peter IV of Bulgaria, was a 12th-century Bulgarian tsar who co-led the successful uprising that restored the Bulgarian Empire after Byzantine rule.
- 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_69e0b51d8a308190b09113b3b3f9bc15 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8afa6afcc8190a1f5c599c11d2135 |
completed | April 22, 2026, 11:23 a.m. |
Created at: April 16, 2026, 5:08 p.m.