Triple
T1638654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarl Waldemar Lindeberg |
E35416
|
entity |
| Predicate | middleName |
P143
|
FINISHED |
| Object |
Waldemar
Waldemar is a masculine given name of Germanic origin, historically associated with Scandinavian and Central European nobility and notable figures.
|
E252102
|
NE FINISHED |
How this triple was built (4 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: Waldemar | Statement: [Jarl Waldemar Lindeberg, middleName, Waldemar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Waldemar Context triple: [Jarl Waldemar Lindeberg, middleName, Waldemar]
-
A.
Gustav
Gustav is a masculine given name of German origin, borne by several notable historical figures including scientists, artists, and royalty.
-
B.
Gustaf
Gustaf is the given name of Carl Gustaf Emil Mannerheim, the Finnish military leader and statesman who served as Commander-in-Chief during World War II and later as President of Finland.
-
C.
Wilhelm
Wilhelm is a Germanic given name, equivalent to William, historically borne by numerous European nobles, rulers, and notable figures.
-
D.
Gerhard
Gerhard is a masculine given name of German origin, historically common in German-speaking countries.
-
E.
Heinrici
Heinrici is a German surname most notably associated with Gotthard Heinrici, a senior Wehrmacht general during World War II.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Waldemar Triple: [Jarl Waldemar Lindeberg, middleName, Waldemar]
Generated description
Waldemar is a masculine given name of Germanic origin, historically associated with Scandinavian and Central European nobility and notable figures.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Waldemar Target entity description: Waldemar is a masculine given name of Germanic origin, historically associated with Scandinavian and Central European nobility and notable figures.
-
A.
Gustav
Gustav is a masculine given name of German origin, borne by several notable historical figures including scientists, artists, and royalty.
-
B.
Gustaf
Gustaf is the given name of Carl Gustaf Emil Mannerheim, the Finnish military leader and statesman who served as Commander-in-Chief during World War II and later as President of Finland.
-
C.
Wilhelm
Wilhelm is a Germanic given name, equivalent to William, historically borne by numerous European nobles, rulers, and notable figures.
-
D.
Gerhard
Gerhard is a masculine given name of German origin, historically common in German-speaking countries.
-
E.
Heinrici
Heinrici is a German surname most notably associated with Gotthard Heinrici, a senior Wehrmacht general during World War II.
- F. None of above. chosen
Provenance (5 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90a1ac46081909f10e793898a9911 |
completed | March 5, 2026, 4:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae7ed8b7a08190a39f4b90fbf68cd9 |
completed | March 9, 2026, 8:03 a.m. |
| NEDg | Description generation | batch_69ae7f701cc48190a5ca5320ac15117d |
completed | March 9, 2026, 8:06 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ae7ff1fb748190961febf3790f03cf |
completed | March 9, 2026, 8:08 a.m. |
Created at: March 4, 2026, 7:28 p.m.