Triple

T4401713
Position Surface form Disambiguated ID Type / Status
Subject Battle of Grüneberg E93632 entity
Predicate namedAfter P63 FINISHED
Object Grüneberg
Grüneberg is a locality in Germany historically known as the site of the Battle of Grüneberg.
 E436919 NE FINISHED

How this triple was built (4 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. Günsberg
    Günsberg is a Swiss municipality located in the canton of Solothurn, known for its scenic setting near the Jura Mountains.
  • B. Luxenberg
    Luxenberg is an alternative spelling or variant form of the name "Luxemburg," which can refer to the European country Luxembourg or the surname of notable individuals such as revolutionary Rosa Luxemburg.
  • C. Böbing
    Böbing is a small municipality in the Weilheim-Schongau district of Bavaria, Germany, known for its rural setting in the Alpine foothills.
  • D. Schöngarth
    Schöngarth is a German surname most notably associated with Eberhard Schöngarth, a high-ranking Nazi SS officer and war criminal during World War II.
  • E. Tureberg
    Tureberg is a central district in Sollentuna Municipality, Sweden, known for housing the municipal center and key public services.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Grüneberg
Triple: [Battle of Grüneberg, namedAfter, Grüneberg]
Generated description
Grüneberg is a locality in Germany historically known as the site of the Battle of Grüneberg.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Grüneberg
Target entity description: Grüneberg is a locality in Germany historically known as the site of the Battle of Grüneberg.
  • A. Günsberg
    Günsberg is a Swiss municipality located in the canton of Solothurn, known for its scenic setting near the Jura Mountains.
  • B. Luxenberg
    Luxenberg is an alternative spelling or variant form of the name "Luxemburg," which can refer to the European country Luxembourg or the surname of notable individuals such as revolutionary Rosa Luxemburg.
  • C. Böbing
    Böbing is a small municipality in the Weilheim-Schongau district of Bavaria, Germany, known for its rural setting in the Alpine foothills.
  • D. Schöngarth
    Schöngarth is a German surname most notably associated with Eberhard Schöngarth, a high-ranking Nazi SS officer and war criminal during World War II.
  • E. Tureberg
    Tureberg is a central district in Sollentuna Municipality, Sweden, known for housing the municipal center and key public services.
  • F. None of above. chosen

Provenance (5 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_69b345158c748190a2c040fce2da9980 completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b352cf218481908d072fec58361f28 completed March 12, 2026, 11:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5f5f788d081909406a938337bd05a completed March 14, 2026, 11:57 p.m.
NEDg Description generation batch_69b5f674c94c81908327336dd4380d2e completed March 14, 2026, 11:59 p.m.
NED2 Entity disambiguation (via description) batch_69b5f719d008819090a35e3597a0089f completed March 15, 2026, 12:02 a.m.
Created at: March 12, 2026, 11:28 p.m.