Triple
T2346527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sweden–Norway union |
E45143
|
entity |
| Predicate | commonInstitution |
P38884
|
FINISHED |
| Object | common monarch |
—
|
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: common monarch | Statement: [Sweden–Norway union, commonInstitution, common monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonInstitution Context triple: [Sweden–Norway union, commonInstitution, common monarch]
-
A.
centralInstitutionOf
Indicates that one institution serves as the primary or main institutional center for another entity, such as an organization, system, or region.
-
B.
establishedInstitution
Indicates that an entity founded, created, or formally set up an institution or organization.
-
C.
associatedWithInstitution
Indicates that an entity has a formal or recognized connection or affiliation with an institution.
-
D.
relatedInstitution
Indicates that there is an institutional connection or association between two entities, such as affiliation, partnership, or organizational linkage.
-
E.
associatedInstitution
Indicates that an entity has a formal connection or affiliation with a particular institution.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abcade3c808190ab3803538ccbe620 |
completed | March 7, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69abc59616a8819099711834e6f1ccd6 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcadd2a0c8190b6973d390e98bd66 |
completed | March 7, 2026, 6:51 a.m. |
Created at: March 4, 2026, 7:52 p.m.