Triple
T370326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emil Adolf von Behring |
E8254
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Emil |
E22883
|
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: Emil | Statement: [Emil Adolf von Behring, givenName, Emil]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Emil Context triple: [Emil Adolf von Behring, givenName, Emil]
-
A.
Emil
chosen
Emil is the given name of Carl Gustaf Emil Mannerheim, the renowned Finnish military leader and statesman who served as President of Finland.
-
B.
Oskar
Oskar is a masculine given name of Germanic origin, commonly used in various European countries.
-
C.
Theodor
Theodor "Ted" Nelson is an American pioneer of information technology best known for coining the term "hypertext" and envisioning global hyperlinked document systems.
-
D.
Karl
Karl is the given name of German Field Marshal Gerd von Rundstedt, a prominent military leader during World War II.
-
E.
Johann
Johann is a given name of Germanic origin commonly used in German-speaking and other European countries.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebff472881909fad81d597425ea6 |
completed | Feb. 28, 2026, 1:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a43e6b0d048190b9623bd47a86ecdd |
completed | March 1, 2026, 1:26 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.