Triple
T31424205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sweden and Denmark |
E801614
|
entity |
| Predicate | sharesRoyalDynasticHistory |
P51869
|
FINISHED |
| Object | House of Oldenburg influence |
—
|
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: House of Oldenburg influence | Statement: [Sweden and Denmark, sharesRoyalDynasticHistory, House of Oldenburg influence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesRoyalDynasticHistory Context triple: [Sweden and Denmark, sharesRoyalDynasticHistory, House of Oldenburg influence]
-
A.
belongsToDynasticHistory
Indicates that something is part of, or associated with, a particular dynastic historical period or lineage.
-
B.
dynasticOrigin
Indicates the historical dynasty or ruling family from which an entity originates or descends.
-
C.
royalTribe
Indicates that an entity belongs to, descends from, or is associated with a tribe that holds royal or ruling status.
-
D.
relatedRoyalHouse
chosen
Indicates a relationship where one royal house is historically, genealogically, or politically connected to another royal house.
-
E.
dynasticLegacy
Indicates that a lineage, tradition, or influence is passed down through successive generations within a dynasty or family line.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: April 30, 2026, 8:51 p.m.