Triple
T15689289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Langmann |
E380282
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Langmann |
E1126092
|
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: Langmann | Statement: [Thomas Langmann, familyName, Langmann]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Langmann Context triple: [Thomas Langmann, familyName, Langmann]
-
A.
Langmann
chosen
Langmann is a French surname notably associated with filmmaker and producer Claude Berri, born Claude Langmann.
-
B.
Lehmann
Lehmann is a German-language surname borne by numerous notable individuals across fields such as science, politics, sports, and the arts.
-
C.
Lorimer
Lorimer is a Scottish surname most notably associated with Sir Robert Stodart Lorimer, a prominent early 20th-century architect and furniture designer.
-
D.
Leumann
Leumann is a surname of likely Germanic or Swiss origin borne by individuals such as academic and public figure Christian Leumann.
-
E.
Lenglern
Lenglern is a village in Lower Saxony, Germany, that forms one of the districts of the municipality of Bovenden near Göttingen.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f4e59988190aaf12f6a07c8f0e4 |
completed | April 16, 2026, 2:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff6ee91340819086c8f51e8eb477aa |
completed | May 9, 2026, 5:29 p.m. |
Created at: April 10, 2026, 4:44 a.m.