Triple
T24705219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Jasmund |
E611870
|
entity |
| Predicate | DanishForceType |
P157189
|
FINISHED |
| Object | steam frigates and smaller vessels |
—
|
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: steam frigates and smaller vessels | Statement: [Battle of Jasmund, DanishForceType, steam frigates and smaller vessels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DanishForceType Context triple: [Battle of Jasmund, DanishForceType, steam frigates and smaller vessels]
-
A.
FinnishForceType
Indicates a classification relationship where an entity is identified as a specific type or category of Finnish military or security force.
-
B.
aimOfDanishForces
Indicates that a specified objective or goal is the intended aim or mission of the Danish military forces.
-
C.
DanishCommander
Indicates that an individual holds or held a commanding military role associated with Denmark.
-
D.
PrussianForceType
Indicates the specific type or classification of a military force associated with Prussia.
-
E.
strengthDenmark
Indicates a measure or characterization of Denmark’s power, influence, or robustness in a given context.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f422add8508190a76e56cfa756eeb8 |
completed | May 1, 2026, 3:49 a.m. |
Created at: April 18, 2026, 3:23 a.m.