Triple
T24981343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hohenfels, Germany |
E625173
|
entity |
| Predicate | militaryTrainingType |
P157889
|
FINISHED |
| Object | counterinsurgency training |
—
|
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: counterinsurgency training | Statement: [Hohenfels, Germany, militaryTrainingType, counterinsurgency training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryTrainingType Context triple: [Hohenfels, Germany, militaryTrainingType, counterinsurgency training]
-
A.
militaryTrainingType
chosen
Indicates the specific kind or category of military training associated with an entity or event.
-
B.
militaryTrainingFocus
Indicates that the primary emphasis or specialization of a subject’s military training is on a particular skill, domain, or operational area.
-
C.
navalTrainingType
Indicates the specific kind or category of naval training associated with an entity.
-
D.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
E.
providesTrainingFor
Indicates that one entity delivers or conducts training activities intended to develop the skills or knowledge of another entity.
- F. None of above.
Provenance (3 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:02 a.m.