Triple
T16407722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David L. Lander |
E398478
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Landau |
E334540
|
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: Landau | Statement: [David L. Lander, familyName, Landau]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Landau Context triple: [David L. Lander, familyName, Landau]
-
A.
Landau
chosen
Landau is a surname most famously associated with Lev Landau, the Nobel Prize–winning Soviet theoretical physicist known for his groundbreaking work in quantum mechanics and condensed matter physics.
-
B.
Landau
Landau is a historic fortified town in southwestern Germany’s Rhineland-Palatinate, long valued for its strategic military position in Europe.
-
C.
Oppenhausen
Oppenhausen is a district or locality within the town of Boppard in the Rhineland-Palatinate region of Germany.
-
D.
Lippinghausen
Lippinghausen is a locality within the municipality of Hiddenhausen in the German state of North Rhine-Westphalia.
-
E.
Balkhausen
Balkhausen is a district within the town of Kerpen in North Rhine-Westphalia, Germany.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32870e44c8190aae7bc6e6022ceb7 |
completed | April 18, 2026, 6:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a003c64a05c8190a59e800ce2318052 |
completed | May 10, 2026, 8:05 a.m. |
Created at: April 10, 2026, 5:09 a.m.