Triple
T15380918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hildesheim district |
E367796
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Sarstedt |
E297421
|
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: Sarstedt | Statement: [Hildesheim district, contains, Sarstedt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sarstedt Context triple: [Hildesheim district, contains, Sarstedt]
-
A.
Sarstedt
chosen
Sarstedt is a small town in Lower Saxony, Germany, situated near Hanover and known for its location along the River Leine.
-
B.
Garstedt
Garstedt is a former independent municipality in northern Germany that now forms part of the city of Norderstedt in Schleswig-Holstein.
-
C.
Delbrück
Delbrück is a German surname most notably associated with Nobel Prize–winning biophysicist Max Delbrück and several other prominent figures in science and humanities.
-
D.
Ramstedt
Ramstedt is a Finnish surname most notably borne by linguist and diplomat Gustaf John Ramstedt, known for his pioneering work in Altaic and Mongolic studies.
-
E.
Biesterfeld
Biesterfeld was a historic estate in the Principality of Lippe that served as the ancestral seat of the Lippe-Biesterfeld noble line.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e61928c81908852c355d537ed9c |
completed | April 16, 2026, 1:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff0b5996408190afab2221d38e0027 |
completed | May 9, 2026, 10:24 a.m. |
Created at: April 10, 2026, 3:19 a.m.