Triple
T2106607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eino Leino |
E42408
|
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: [Eino Leino, givenName, Leopold]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leopold Context triple: [Eino Leino, 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbaddeb148190b728bce7a7b041fb |
completed | March 7, 2026, 5:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae306e040081909334f2a70036c26e |
completed | March 9, 2026, 2:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.