Triple
T9276364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Stralsund (1370) |
E222957
|
entity |
| Predicate | securedDominanceOver |
P2547
|
FINISHED |
| Object | Baltic Sea trade |
—
|
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: Baltic Sea trade | Statement: [Treaty of Stralsund (1370), securedDominanceOver, Baltic Sea trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securedDominanceOver Context triple: [Treaty of Stralsund (1370), securedDominanceOver, Baltic Sea trade]
-
A.
confirmedDominanceOf
Indicates that one entity has been verified or officially recognized as having dominance or superiority over another entity.
-
B.
dominantOn
chosen
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
-
C.
dominantDuring
Indicates that one entity holds a prevailing or controlling influence over another specifically within a given time period or interval.
-
D.
dominatedBy
Indicates that one entity is under the control, influence, or overpowering authority of another entity.
-
E.
brokeDominanceOf
Indicates that one entity disrupted, ended, or significantly reduced another entity’s prevailing control, influence, or supremacy.
- 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd07c71b5c8190b5b7b5ab4224e9d3 |
completed | April 1, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:34 p.m.