Triple
T18184459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sigurd |
E435371
|
entity |
| Predicate | isCognateWith |
P2527
|
FINISHED |
| Object | Sigfrid |
—
|
NE NERFINISHED |
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: Sigfrid | Statement: [Sigurd, isCognateWith, Sigfrid]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sigfrid Context triple: [Sigurd, isCognateWith, Sigfrid]
-
A.
Sigfrid
chosen
Sigfrid is a masculine given name of Scandinavian origin, notably borne by Swedish industrialist and long-serving International Olympic Committee president Sigfrid Edström.
-
B.
Sigfred
Sigfred was a Viking leader known for commanding Norse forces during the late 9th-century siege of Paris.
-
C.
Sigurd
Sigurd is a masculine given name of Old Norse origin, historically associated with legendary heroes and figures in Scandinavian culture.
-
D.
Sigfrid of Sweden
Sigfrid of Sweden was an English missionary bishop and saint traditionally credited with helping to introduce and spread Christianity in early medieval Sweden.
-
E.
Sigurd Hring
Sigurd Hring is a legendary Scandinavian king and warrior of Norse sagas, often associated with the early Viking Age and linked to the lineage of the famed hero Ragnar Lodbrok.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dffd0abc81908cc07d28bdc3d48f |
completed | April 19, 2026, 2 p.m. |
Created at: April 10, 2026, 10:31 a.m.