Triple
T34161505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woden |
E876287
|
entity |
| Predicate | nameCognate |
P51524
|
FINISHED |
| Object | Old Norse Odin |
—
|
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: Old Norse Odin | Statement: [Woden, nameCognate, Old Norse Odin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameCognate Context triple: [Woden, nameCognate, Old Norse Odin]
-
A.
nameCognateOf
chosen
Indicates that two names share a common linguistic origin or form, typically due to derivation from the same root or historical source.
-
B.
cognateOf
Indicates that two linguistic forms share a common historical origin, typically descending from the same ancestral word.
-
C.
hasCognate
Indicates that two linguistic forms in different languages share a common historical origin, typically descending from the same ancestral word.
-
D.
possibleCognateWith
Indicates a relationship where one term is considered a potential cognate of another, suggesting they may share a common historical linguistic origin.
-
E.
cognate
Indicates that two linguistic forms share a common historical origin, typically deriving from the same ancestral word.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fdedf708190ab68c2d567e086d0 |
completed | May 3, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.