Triple
T30027512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raðulfr |
E762918
|
entity |
| Predicate | hasModernScandinavianEquivalent |
P174862
|
FINISHED |
| Object | Ralf |
—
|
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: Ralf | Statement: [Raðulfr, hasModernScandinavianEquivalent, Ralf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernScandinavianEquivalent Context triple: [Raðulfr, hasModernScandinavianEquivalent, Ralf]
-
A.
hasScandinavianForm
Indicates that one entity is a Scandinavian-language form or variant of another entity.
-
B.
equivalentNameInScandinavianLanguages
chosen
Indicates that two names are equivalent or correspond to each other specifically within Scandinavian languages.
-
C.
norseEquivalent
Indicates that one entity is the counterpart or analogue of another within Norse mythology or Norse cultural context.
-
D.
hasModernStandardForms
Indicates that an entity possesses one or more contemporary, standardized versions or representations of itself.
-
E.
meaningInModernScandinavianLanguages
Indicates that something has a particular meaning or sense when used in contemporary Scandinavian languages.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 29, 2026, 6:49 p.m.