Triple
T7302898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reideburg |
E167901
|
entity |
| Predicate | hasNameInLanguage |
P15
|
FINISHED |
| Object | Reideburg |
E167901
|
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: Reideburg | Statement: [Reideburg, hasNameInLanguage, Reideburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Reideburg Context triple: [Reideburg, hasNameInLanguage, Reideburg]
-
A.
Reideburg
chosen
Reideburg is a district of Halle (Saale) in the German state of Saxony-Anhalt, known as the birthplace of prominent politician Hans-Dietrich Genscher.
-
B.
Reinswald
Reinswald is a small alpine village and ski resort located in the Sarntal Alps of South Tyrol in northern Italy.
-
C.
Hesselberg
Hesselberg is a prominent hill in Bavaria, Germany, known as the highest elevation of the Franconian Alb region.
-
D.
Lutterberg
Lutterberg is a village in Lower Saxony, Germany, historically notable as the site of the 1758 Battle of Lutterberg during the Seven Years' War.
-
E.
Aegidienberg
Aegidienberg is a district of the town of Bad Honnef in North Rhine-Westphalia, Germany, known for its scenic location in the Siebengebirge region.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebb2261c8190ae9095c8e110b528 |
completed | March 27, 2026, 8:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7e558098c819091562566c59332e2 |
completed | March 28, 2026, 2:27 p.m. |
Created at: March 27, 2026, 3:01 p.m.