Triple

T17804902
Position Surface form Disambiguated ID Type / Status
Subject German Army Group F E444529 entity
Predicate militaryBranch P253 FINISHED
Object Heer 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: Heer | Statement: [German Army Group F, militaryBranch, Heer]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heer
Context triple: [German Army Group F, militaryBranch, Heer]
  • A. Heer chosen
    The Heer was the land-based component of Nazi Germany’s armed forces, serving as its primary army during World War II.
  • B. Heer
    Heer is the tragic heroine of the classic Punjabi romantic epic "Heer Ranjha," renowned as a symbol of eternal love and devotion.
  • C. Reuver
    Reuver is a village in the Dutch province of Limburg, situated along the River Meuse and served by the Maaslijn railway.
  • D. Heer Command
    Heer Command is the central high-level command authority responsible for overseeing and directing the German Army (Heer) within the Bundeswehr.
  • E. Heris
    Heris is a city in northwestern Iran known for its traditional handwoven carpets and rugs.
  • 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_69d8b9efe370819095cd219b143ae727 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48802bcfc8190a138164d11081ab8 completed April 19, 2026, 7:45 a.m.
Created at: April 10, 2026, 10:14 a.m.