Triple
T24705223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Jasmund |
E611870
|
entity |
| Predicate | DanishObjective |
P62182
|
FINISHED |
| Object | maintain control of Baltic Sea routes |
—
|
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: maintain control of Baltic Sea routes | Statement: [Battle of Jasmund, DanishObjective, maintain control of Baltic Sea routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DanishObjective Context triple: [Battle of Jasmund, DanishObjective, maintain control of Baltic Sea routes]
-
A.
aimOfDanishForces
chosen
Indicates that a specified objective or goal is the intended aim or mission of the Danish military forces.
-
B.
officialNameInDanish
Indicates the officially recognized name of an entity when expressed in the Danish language.
-
C.
AustrianObjective
Indicates that an entity has an objective, goal, or purpose specifically associated with Austria or Austrian context.
-
D.
hasNameInDanish
Indicates that an entity is associated with a specific name expressed in the Danish language.
-
E.
PolishObjective
Indicates that an entity is the target or goal of a polishing action or process.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 3:23 a.m.