Triple
T34704925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Schleswig |
E1000474
|
entity |
| Predicate | currentOfficialDanishTerm |
P5200
|
FINISHED |
| Object | Sønderjylland |
—
|
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: Sønderjylland | Statement: [North Schleswig, currentOfficialDanishTerm, Sønderjylland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentOfficialDanishTerm Context triple: [North Schleswig, currentOfficialDanishTerm, Sønderjylland]
-
A.
officialNameInDanish
chosen
Indicates the officially recognized name of an entity when expressed in the Danish language.
-
B.
hasNameInDanish
Indicates that an entity is associated with a specific name expressed in the Danish language.
-
C.
hasDanishNameMeaning
Indicates that an entity has a Danish name whose semantic meaning or etymology is being specified.
-
D.
shortNameInDanish
Indicates that one entity is the short or abbreviated name of another entity when expressed in Danish.
-
E.
meaningInModernScandinavianLanguages
Indicates that something has a particular meaning or sense when used in contemporary Scandinavian languages.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff45793d5c81909dc503ad1f714ee2 |
completed | May 9, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69ff41cb0e088190a6e9b03cb20e5fad |
completed | May 9, 2026, 2:16 p.m. |
Created at: May 3, 2026, 3:59 p.m.