Triple
T3920574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inatsisartut |
E88947
|
entity |
| Predicate | alsoKnownAsLanguage |
P17843
|
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: [Inatsisartut, alsoKnownAsLanguage, Danish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoKnownAsLanguage Context triple: [Inatsisartut, alsoKnownAsLanguage, Danish]
-
A.
recognizedAsDistinctLanguageFrom
Indicates that one language is formally acknowledged or treated as a separate and distinct language from another, rather than as a dialect or variant of it.
-
B.
closelyAssociatedLanguage
Indicates that one language is closely connected to another, such as through frequent co-use, mutual influence, or strong cultural or regional association.
-
C.
alsoTranslatedAs
Indicates that something has an alternative translation or rendering in another language or form.
-
D.
isSpokenAs
chosen
Indicates that one entity is used as the spoken or verbal form of another entity (e.g., a word, name, or phrase).
-
E.
alsoKnownAs
Indicates that one entity is an alternative name, alias, or designation for another entity.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.