Triple
T26276441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freden i Lund |
E660583
|
entity |
| Predicate | confirmedPreviousTreaty |
P111623
|
FINISHED |
| Object | Treaty of Roskilde (1658) |
—
|
NE NERFINISHED |
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: Treaty of Roskilde (1658) | Statement: [Freden i Lund, confirmedPreviousTreaty, Treaty of Roskilde (1658)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confirmedPreviousTreaty Context triple: [Freden i Lund, confirmedPreviousTreaty, Treaty of Roskilde (1658)]
-
A.
confirmedTreaty
chosen
Indicates that an entity has formally approved, ratified, or validated a treaty, making the agreement officially recognized or in force.
-
B.
treatyAfter
Indicates that a treaty or formal agreement was established after a specified prior event, condition, or relationship between the entities.
-
C.
signedTreatyAt
Indicates that an entity formally entered into and endorsed a treaty at a specific location.
-
D.
treatyConcluded
Indicates that a formal agreement or treaty has been officially finalized and brought into force between the involved parties.
-
E.
cededByTreaty
Indicates that control or ownership of one entity was formally transferred to another entity as a result of a treaty or formal agreement.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 9:56 p.m.