Triple
T23299027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niklas Luhmann |
E590250
|
entity |
| Predicate | placeOfDeath |
P21
|
FINISHED |
| Object | Oerlinghausen |
—
|
NE NERFINISHED |
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: Oerlinghausen | Statement: [Niklas Luhmann, placeOfDeath, Oerlinghausen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oerlinghausen Context triple: [Niklas Luhmann, placeOfDeath, Oerlinghausen]
-
A.
Oerlinghausen
chosen
Oerlinghausen is a small town in the German state of North Rhine-Westphalia, known for its scenic Teutoburg Forest surroundings and historical roots.
-
B.
Sprockhövel
Sprockhövel is a small town in North Rhine-Westphalia, Germany, known for its historical coal mining heritage and location in the hilly Ruhr region.
-
C.
Ehringshausen
Ehringshausen is a municipality in the Lahn-Dill district of the German state of Hesse.
-
D.
Wedemark
Wedemark is a municipality in Lower Saxony, Germany, located north of Hanover and known for its semi-rural character and commuter links to the city.
-
E.
Nordhorn
Nordhorn is a town in Lower Saxony, Germany, known as the administrative center of the Grafschaft Bentheim district near the Dutch border.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196d133448190bf350a9f51c1531c |
completed | April 29, 2026, 5:27 a.m. |
Created at: April 17, 2026, 5:03 p.m.