Triple
T19978836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gutar |
E493761
|
entity |
| Predicate | historicalLanguageVarietyOf |
P7165
|
FINISHED |
| Object | Old Norse |
—
|
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 | Statement: [Gutar, historicalLanguageVarietyOf, Old Norse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalLanguageVarietyOf Context triple: [Gutar, historicalLanguageVarietyOf, Old Norse]
-
A.
historicalLanguage
chosen
Indicates that one language is a historical or earlier form/ancestor of another language.
-
B.
partOfLinguisticVariety
Indicates that one linguistic variety (such as a dialect, register, or style) is a constituent or subset of another, broader linguistic variety.
-
C.
historicalDialect
Indicates that one dialect is a historically earlier or ancestral form of another dialect.
-
D.
historicalLanguageStatus
Indicates that a language had a particular official, social, or functional status during a past historical period.
-
E.
historicalLanguageRegion
Indicates that a language was historically spoken or used within a particular geographic region, regardless of its current status there.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d11108481908241a2a96a795a7d |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:27 p.m.