Triple
T20017015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windhund Division |
E494747
|
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: [Windhund Division, militaryBranch, Heer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heer Context triple: [Windhund Division, 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.
Herouël
Herouël is a small commune in northern France, notable as the birthplace of French Revolutionary prosecutor Antoine Quentin Fouquier-Tinville.
-
D.
Reuver
Reuver is a village in the Dutch province of Limburg, situated along the River Meuse and served by the Maaslijn railway.
-
E.
Heer Command
Heer Command is the central high-level command authority responsible for overseeing and directing the German Army (Heer) within the Bundeswehr.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623cb8188190b95913ffed895930 |
completed | April 20, 2026, 5:28 p.m. |
Created at: April 11, 2026, 3:34 p.m.