Triple
T3866132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friedrich Robert Faehlmann |
E91858
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object |
Faehlmann
Faehlmann is a surname most notably associated with Friedrich Robert Faehlmann, a prominent 19th-century Estonian writer, physician, and folklorist.
|
E395954
|
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: Faehlmann | Statement: [Friedrich Robert Faehlmann, familyName, Faehlmann]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Faehlmann Context triple: [Friedrich Robert Faehlmann, familyName, Faehlmann]
-
A.
Hammann
Hammann is a German-origin surname borne by various notable individuals in fields such as aviation, music, and academia.
-
B.
Fuhse
Fuhse is a river in Lower Saxony, Germany, that flows through several towns before joining the Aller River.
-
C.
Edelmann
Edelmann is a surname of German origin borne by various individuals across fields such as music, sports, and academia.
-
D.
Gütermann
Gütermann is a German surname most notably associated with the Gütermann family involved in industry and manufacturing, particularly in the production of sewing threads.
-
E.
Hartmann
Hartmann is a German surname borne by numerous notable individuals across fields such as music, philosophy, and aviation.
- 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: Faehlmann Triple: [Friedrich Robert Faehlmann, familyName, Faehlmann]
Generated description
Faehlmann is a surname most notably associated with Friedrich Robert Faehlmann, a prominent 19th-century Estonian writer, physician, and folklorist.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Faehlmann Target entity description: Faehlmann is a surname most notably associated with Friedrich Robert Faehlmann, a prominent 19th-century Estonian writer, physician, and folklorist.
-
A.
Hammann
Hammann is a German-origin surname borne by various notable individuals in fields such as aviation, music, and academia.
-
B.
Fuhse
Fuhse is a river in Lower Saxony, Germany, that flows through several towns before joining the Aller River.
-
C.
Edelmann
Edelmann is a surname of German origin borne by various individuals across fields such as music, sports, and academia.
-
D.
Gütermann
Gütermann is a German surname most notably associated with the Gütermann family involved in industry and manufacturing, particularly in the production of sewing threads.
-
E.
Hartmann
Hartmann is a German surname borne by numerous notable individuals across fields such as music, philosophy, and aviation.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec3b8d988190b56d42ac1521e19c |
completed | March 9, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b512410f38819089adccf0a476dd8f |
completed | March 14, 2026, 7:46 a.m. |
| NEDg | Description generation | batch_69b512f3504c8190be940148a4f726e9 |
completed | March 14, 2026, 7:49 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69b5172b369c8190956d7c54943225cd |
completed | March 14, 2026, 8:07 a.m. |
Created at: March 9, 2026, 3:19 p.m.