Triple
T5670821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Roskilde |
E124970
|
entity |
| Predicate | requiredDenmarkTo |
P6501
|
FINISHED |
| Object | renounceClaimsToScania |
—
|
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: renounceClaimsToScania | Statement: [Treaty of Roskilde, requiredDenmarkTo, renounceClaimsToScania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredDenmarkTo Context triple: [Treaty of Roskilde, requiredDenmarkTo, renounceClaimsToScania]
-
A.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
B.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
C.
demanded
chosen
Indicates that one entity forcefully or insistently requested something from another entity.
-
D.
approvalRequirement
Indicates that one entity must grant permission or authorization before another entity’s action, decision, or state change can proceed.
-
E.
requiresDispositionOf
Indicates that one entity must be appropriately handled, removed, or otherwise disposed of as a condition related to another entity or situation.
- 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.