Triple
T8253134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spies |
E193003
|
entity |
| Predicate | hasNotableBearer |
P458
|
FINISHED |
| Object |
Heinrich Spies
Heinrich Spies is a person notable enough to be recognized as a significant bearer of the surname Spies.
|
E736951
|
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: Heinrich Spies | Statement: [Spies, hasNotableBearer, Heinrich Spies]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heinrich Spies Context triple: [Spies, hasNotableBearer, Heinrich Spies]
-
A.
Friedrich Spies
Friedrich Spies is a notable individual who shares his surname with others recognized under the name Spies.
-
B.
Otto Steinbrinck
Otto Steinbrinck was a German industrialist and SS officer who was prosecuted as a war criminal for his role in Nazi economic enterprises during the Flick Trial after World War II.
-
C.
Hermann Schmitz
Hermann Schmitz was a German industrialist who served as a leading executive of IG Farben and was later convicted for his role in the company’s activities during the Nazi era.
-
D.
Karl Spies
Karl Spies is an individual notable enough to be recognized as a namesake of the surname Spies.
-
E.
Heinrich Schmidt
Heinrich Schmidt is a relatively common German personal name shared by multiple individuals across various professions and historical periods.
- 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: Heinrich Spies Triple: [Spies, hasNotableBearer, Heinrich Spies]
Generated description
Heinrich Spies is a person notable enough to be recognized as a significant bearer of the surname Spies.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Heinrich Spies Target entity description: Heinrich Spies is a person notable enough to be recognized as a significant bearer of the surname Spies.
-
A.
Friedrich Spies
Friedrich Spies is a notable individual who shares his surname with others recognized under the name Spies.
-
B.
Otto Steinbrinck
Otto Steinbrinck was a German industrialist and SS officer who was prosecuted as a war criminal for his role in Nazi economic enterprises during the Flick Trial after World War II.
-
C.
Hermann Schmitz
Hermann Schmitz was a German industrialist who served as a leading executive of IG Farben and was later convicted for his role in the company’s activities during the Nazi era.
-
D.
Karl Spies
Karl Spies is an individual notable enough to be recognized as a namesake of the surname Spies.
-
E.
Heinrich Schmidt
Heinrich Schmidt is a relatively common German personal name shared by multiple individuals across various professions and historical periods.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78cbc7cc81909931440e95d6e691 |
completed | March 31, 2026, 7:33 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce392feb048190a2adaee594127b0c |
completed | April 2, 2026, 9:38 a.m. |
| NEDg | Description generation | batch_69ce3ad9a3a88190929a6c6ae7ee58cf |
completed | April 2, 2026, 9:46 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ce3cc54d888190ae86b787afc38f7b |
completed | April 2, 2026, 9:54 a.m. |
Created at: March 30, 2026, 5:48 p.m.