Triple
T33933523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle for Hill 70 |
E869966
|
entity |
| Predicate | GermanResponse |
P177933
|
FINISHED |
| Object | multiple counterattacks |
—
|
LITERAL 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: multiple counterattacks | Statement: [Battle for Hill 70, GermanResponse, multiple counterattacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GermanResponse Context triple: [Battle for Hill 70, GermanResponse, multiple counterattacks]
-
A.
GermanPerspective
Indicates that something is viewed, interpreted, or presented from a German point of view, context, or frame of reference.
-
B.
objectiveGermany
Indicates that an entity has Germany as its objective, target, or goal in a given context.
-
C.
germanPart
Indicates that one entity is a component, section, or segment that belongs to or forms part of something specifically in a German context (e.g., language, jurisdiction, or origin).
-
D.
GermanEditionURL
Indicates the URL where the German-language edition or version of an item can be accessed.
-
E.
abbreviationGerman
Indicates that one term is the German-language abbreviation or shortened form of another term.
- F. None of above. chosen
Provenance (4 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f7064d37388190993b2a7305a02b9f |
completed | May 3, 2026, 8:24 a.m. |
Created at: May 1, 2026, 1:49 a.m.