Triple
T26497070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kolding |
E669310
|
entity |
| Predicate | armedForce1 |
P39448
|
FINISHED |
| Object | Danish Army |
—
|
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: Danish Army | Statement: [Battle of Kolding, armedForce1, Danish Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armedForce1 Context triple: [Battle of Kolding, armedForce1, Danish Army]
-
A.
armedForcesCategory
Indicates the classification of a country's or group's military forces into a specific type or category (e.g., army, navy, air force, paramilitary).
-
B.
militaryOrganization
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
-
C.
groundForces
Indicates that one entity deploys, commands, or involves military forces operating on land in relation to another entity or context.
-
D.
armedForcesInvolved
chosen
Indicates that the relationship or event involves the participation or presence of military or armed forces.
-
E.
militaryBranchOfGovernment
Indicates that a military organization functions as an official branch or component of a government.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613573c548190a4a25a430a89fbf4 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:09 a.m.