Triple
T18244710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Grüneberg |
E436919
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Grüneberg |
—
|
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: Grüneberg | Statement: [Battle of Grüneberg, namedAfter, Grüneberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Grüneberg Context triple: [Battle of Grüneberg, namedAfter, Grüneberg]
-
A.
Grüneberg
chosen
Grüneberg is a locality in Germany historically known as the site of the Battle of Grüneberg.
-
B.
Grotenberge
Grotenberge is a village in East Flanders, Belgium, that forms part of the municipality of Zottegem.
-
C.
Leuenberg
Leuenberg is a village in Switzerland known as the site where major European Protestant churches concluded the Leuenberg Agreement on church fellowship.
-
D.
Steinbühl
Steinbühl is a district of the German city of Nuremberg, known as an urban residential area served by the Nürnberg-Steinbühl railway station.
-
E.
Stollberg
Stollberg is a historic town in Saxony, Germany, known for its role in the Ore Mountains mining region and its traditional mining heritage.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f7e5d63081908d0e6249578867a1 |
completed | April 19, 2026, 3:42 p.m. |
Created at: April 10, 2026, 10:33 a.m.