Triple
T23961724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Als |
E603945
|
entity |
| Predicate | impactOnDenmark |
P154057
|
FINISHED |
| Object | contributed to Denmark’s territorial losses in 1864 |
—
|
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: contributed to Denmark’s territorial losses in 1864 | Statement: [Battle of Als, impactOnDenmark, contributed to Denmark’s territorial losses in 1864]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnDenmark Context triple: [Battle of Als, impactOnDenmark, contributed to Denmark’s territorial losses in 1864]
-
A.
effectOnSweden
Indicates the impact or consequences that something has on Sweden.
-
B.
impactOnScotland
Indicates the effect or consequences that something has specifically on Scotland.
-
C.
effectOnNorway
Indicates the impact or influence that one entity, event, or condition has on Norway.
-
D.
effectOnFinland
Indicates the impact or influence that something has on Finland, such as how an event, action, or condition affects the country.
-
E.
nationalImpact
Indicates that something has a significant effect or influence at the level of an entire nation.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0dac8e081908286e8d8d30784ee |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:23 p.m.