Triple
T35085594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sól |
E1012565
|
entity |
| Predicate | equivalentInProtoGermanic |
P182562
|
FINISHED |
| Object | Sunnōn |
—
|
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: Sunnōn | Statement: [Sól, equivalentInProtoGermanic, Sunnōn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equivalentInProtoGermanic Context triple: [Sól, equivalentInProtoGermanic, Sunnōn]
-
A.
cognateInOldHighGerman
Indicates that a word or term has a corresponding cognate form in Old High German, reflecting a shared historical linguistic origin.
-
B.
cognateInGerman
Indicates that a given word or term has a cognate (etymologically related counterpart) in the German language.
-
C.
hasLanguageFormOf
Indicates that one entity is a specific linguistic form, expression, or realization of the language used by another entity.
-
D.
norseEquivalent
Indicates that one entity is the counterpart or analogue of another within Norse mythology or Norse cultural context.
-
E.
nameCognateOf
Indicates that two names share a common linguistic origin or form, typically due to derivation from the same root or historical source.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:01 p.m.