Triple
T10374147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convention of Moss |
E244458
|
entity |
| Predicate | effectOnSweden |
P93646
|
FINISHED |
| Object | secured dynastic union with Norway |
—
|
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: secured dynastic union with Norway | Statement: [Convention of Moss, effectOnSweden, secured dynastic union with Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnSweden Context triple: [Convention of Moss, effectOnSweden, secured dynastic union with Norway]
-
A.
effectOnAustria
Indicates the impact or influence that one entity, event, or action has on Austria.
-
B.
effectOnSpain
Indicates a relationship where one entity produces an influence, change, or consequence specifically affecting Spain.
-
C.
effectOnFrance
Indicates the impact, influence, or consequences that something has on France.
-
D.
effectOnUnitedStates
Indicates the impact, influence, or consequences that something has on the United States.
-
E.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9804e708190b15f5d38cac9c4c1 |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e944fac4819093b0312aa0efd729 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:02 p.m.