Triple
T20404494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danish invasion of Scania 1709–1710 |
E500429
|
entity |
| Predicate | outcomeForDenmark–Norway |
P59870
|
FINISHED |
| Object | failure to regain Scania |
—
|
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: failure to regain Scania | Statement: [Danish invasion of Scania 1709–1710, outcomeForDenmark–Norway, failure to regain Scania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForDenmark–Norway Context triple: [Danish invasion of Scania 1709–1710, outcomeForDenmark–Norway, failure to regain Scania]
-
A.
effectOnNorway
Indicates the impact or influence that one entity, event, or condition has on Norway.
-
B.
unionWithSwedenEnd
Indicates the point in time or event at which a political or territorial union with Sweden comes to an end.
-
C.
strengthDenmark
Indicates a measure or characterization of Denmark’s power, influence, or robustness in a given context.
-
D.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
E.
gainedByFinlandThrough
Indicates that something was obtained, acquired, or achieved as a result of actions or circumstances involving Finland.
- 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6799161c48190825eca3027d1aa51 |
completed | April 20, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:29 a.m.