Triple
T14400742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fólkvangr |
E357061
|
entity |
| Predicate | hasPrimarySourceLanguage |
P2925
|
FINISHED |
| Object | Old Norse literature |
—
|
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: Old Norse literature | Statement: [Fólkvangr, hasPrimarySourceLanguage, Old Norse literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySourceLanguage Context triple: [Fólkvangr, hasPrimarySourceLanguage, Old Norse literature]
-
A.
hasPrimaryLanguage1
Indicates that an entity’s main or most commonly used language is the specified language.
-
B.
hasPrimaryLanguageBranch
Indicates that an entity’s main or dominant language belongs to a specified language branch or family.
-
C.
hasPrimaryVernacularLanguageFamily
Indicates that an entity’s main vernacular language belongs to a specified language family.
-
D.
hasPrimaryLanguageSubbranch
Indicates that one language subbranch is the main or principal subbranch associated with a given language or language family.
-
E.
languageOfSources
chosen
Indicates that the specified language is the language in which the referenced sources or source materials are expressed.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de908500048190bb6a20fe318d5c62 |
completed | April 14, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:17 a.m.