Triple
T16032956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nietzsche family graves |
E388892
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Röcken |
E89670
|
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: Röcken | Statement: [Nietzsche family graves, locatedIn, Röcken]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Röcken Context triple: [Nietzsche family graves, locatedIn, Röcken]
-
A.
Röcken
chosen
Röcken is a small village in Saxony-Anhalt, Germany, best known as the birthplace of the philosopher Friedrich Nietzsche.
-
B.
Rößel
Rößel is the former German name of the historic town now known as Reszel, located in northeastern Poland.
-
C.
Felsberg
Felsberg is a settlement located in the historical region of Westphalia in western Germany.
-
D.
Rollingergrund
Rollingergrund is a district of Luxembourg City known for its residential character and proximity to central neighborhoods like Limpertsberg.
-
E.
Schöngarth
Schöngarth is a German surname most notably associated with Eberhard Schöngarth, a high-ranking Nazi SS officer and war criminal during World War II.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e183396a708190b53a589f6ac2c5bc |
completed | April 17, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffe474f89c819086db832b793c15ed |
completed | May 10, 2026, 1:50 a.m. |
Created at: April 10, 2026, 4:56 a.m.