Triple
T15260080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sigfrid of Sweden |
E364750
|
entity |
| Predicate | linkedToProcess |
P4106
|
FINISHED |
| Object | conversion of Scandinavian pagans |
—
|
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: conversion of Scandinavian pagans | Statement: [Sigfrid of Sweden, linkedToProcess, conversion of Scandinavian pagans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToProcess Context triple: [Sigfrid of Sweden, linkedToProcess, conversion of Scandinavian pagans]
-
A.
linkedProcess
Indicates that one process is associated with or connected to another process in a meaningful or dependent way.
-
B.
partOfProcess
chosen
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
-
C.
linkedToResolution
Indicates that something is associated with, or directly connected to, a specific resolution or decision outcome.
-
D.
linkedProgram
Indicates that one program is associated or connected to another program in a meaningful or dependent way.
-
E.
linkedToPort
Indicates that one entity is connected or associated with a specific port, such as a network, hardware, or interface port.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084d11148190919eef8e55569bb9 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.