Triple
T15075152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto Warburg |
E379980
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Warburg |
E152756
|
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: Warburg | Statement: [Otto Warburg, familyName, Warburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Warburg Context triple: [Otto Warburg, familyName, Warburg]
-
A.
Warburg
chosen
Warburg is a prominent German-Jewish banking and philanthropic family historically influential in international finance and economic policy.
-
B.
Warburg
Warburg is a historic small city in the German state of Hesse, known for its well-preserved medieval old town and hilltop castle.
-
C.
Landsberg
Landsberg is a town in the Saalekreis district of the German state of Saxony-Anhalt.
-
D.
Hadern
Hadern is a borough in the southwest of Munich, Germany, known for its residential character and the large Waldfriedhof cemetery.
-
E.
Westphal
Westphal is a German-origin surname borne by various notable individuals in fields such as sports, politics, and academia.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff7fb60448190b454386dd762644d |
completed | April 15, 2026, 8:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fea5d2765481908f101bef483ed02f |
completed | May 9, 2026, 3:11 a.m. |
Created at: April 10, 2026, 3:02 a.m.