Triple
T1529824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordic Americans |
E32414
|
entity |
| Predicate | ancestralLanguages |
P11719
|
FINISHED |
| Object | Danish |
—
|
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: Danish | Statement: [Nordic Americans, ancestralLanguages, Danish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancestralLanguages Context triple: [Nordic Americans, ancestralLanguages, Danish]
-
A.
ancientLanguageFamily
Indicates that one language belongs to or descends from a historically ancient family of related languages.
-
B.
ancientLanguages
Indicates that the related entities are languages that originated in and were used during ancient historical periods.
-
C.
hasLinguisticHeritage
chosen
Indicates that one entity possesses or is associated with the linguistic background, tradition, or ancestry of another entity.
-
D.
influencedLanguageFamily
Indicates that one language family has had a significant impact on the development, structure, or usage of another language family.
-
E.
languageOfEarliestForm
Indicates the language in which the earliest known form or attested version of something (e.g., a text, name, or expression) is recorded.
- 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_69a885ea86308190998f6bc14bb91f8e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a933ddc5a881909cdf503f2bc29bd4 |
completed | March 5, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69a907ae8f688190ad9000ea1e018585 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.