Triple
T35935852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Settlement, Greenland |
E1039301
|
entity |
| Predicate | hasModernNameInDanish |
P90804
|
FINISHED |
| Object | Vesterbygden |
—
|
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: Vesterbygden | Statement: [Western Settlement, Greenland, hasModernNameInDanish, Vesterbygden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernNameInDanish Context triple: [Western Settlement, Greenland, hasModernNameInDanish, Vesterbygden]
-
A.
hasNameInDanish
Indicates that an entity is associated with a specific name expressed in the Danish language.
-
B.
hasModernName
Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
-
C.
hasDanishNameMeaning
Indicates that an entity has a Danish name whose semantic meaning or etymology is being specified.
-
D.
hasModernNameLanguage
chosen
Indicates that the modern name of an entity is expressed in a particular language.
-
E.
isModernName
Indicates that a given name is considered modern or contemporary in usage or origin, as opposed to traditional or historical.
- 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_69f76e24bbd0819096b837d35371639a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 3, 2026, 4:07 p.m.