Triple
T19692650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lippe (region) |
E472873
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Augustdorf |
—
|
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: Augustdorf | Statement: [Lippe (region), hasPart, Augustdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Augustdorf Context triple: [Lippe (region), hasPart, Augustdorf]
-
A.
Augustdorf
chosen
Augustdorf is a municipality in North Rhine-Westphalia, Germany, known for its proximity to the Teutoburg Forest and its significant military presence, including Bundeswehr facilities.
-
B.
Basdorf
Basdorf is a village and district within the municipality of Wandlitz in the state of Brandenburg, Germany.
-
C.
Stedesdorf
Stedesdorf is a small municipality in Lower Saxony, Germany, situated in the East Frisian region.
-
D.
Weiterstadt
Weiterstadt is a town in the German state of Hesse, located near Darmstadt and known for its residential areas and commercial centers.
-
E.
Hennigsdorf
Hennigsdorf is a town in the German state of Brandenburg, located just northwest of Berlin and known for its industrial heritage and proximity to the Havel River.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e64210cddc8190836faa2996a44457 |
completed | April 20, 2026, 3:11 p.m. |
Created at: April 10, 2026, 1:46 p.m.