Triple
T11803073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Jemmingen |
E280675
|
entity |
| Predicate | tacticsUsedByDutch |
P30685
|
FINISHED |
| Object | attempted defensive position near dikes |
—
|
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: attempted defensive position near dikes | Statement: [Battle of Jemmingen, tacticsUsedByDutch, attempted defensive position near dikes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticsUsedByDutch Context triple: [Battle of Jemmingen, tacticsUsedByDutch, attempted defensive position near dikes]
-
A.
DutchCommander
Indicates that an entity serves as a military commander associated with the Netherlands.
-
B.
militaryTacticsUsed
chosen
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
-
C.
effectOnDutchRepublic
Indicates the impact or consequences that something has on the Dutch Republic.
-
D.
tacticsManualUsedBy
Indicates that a tactics manual is utilized or applied by a particular agent or entity.
-
E.
dutchCasualties
Indicates that the relationship specifies the number or occurrence of casualties suffered by Dutch entities in a given event or context.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.