Triple
T31426765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyveke Sigbritsdatter |
E801683
|
entity |
| Predicate | broughtToDenmarkBy |
P171859
|
FINISHED |
| Object | mother |
—
|
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: mother | Statement: [Dyveke Sigbritsdatter, broughtToDenmarkBy, mother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broughtToDenmarkBy Context triple: [Dyveke Sigbritsdatter, broughtToDenmarkBy, mother]
-
A.
broughtToBritainBy
Indicates that something or someone was transported or introduced into Britain by a particular agent or source.
-
B.
introducedToEnglandBy
Indicates that one entity was responsible for bringing or first establishing another entity in England.
-
C.
wereIntroducedBy
Indicates that one entity became known, presented, or brought to the attention of another entity through the action or mediation of a third party.
-
D.
introducedToScotlandBy
Indicates that one entity was responsible for bringing or establishing another entity in Scotland for the first time.
-
E.
cultIntroducedBy
Indicates that a particular cult or religious practice was brought into a place, group, or culture through the agency or influence of a specific person or entity.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a5f656ec81909e02b0b873303adf |
completed | May 3, 2026, 1:33 a.m. |
Created at: April 30, 2026, 8:53 p.m.