Triple
T25680502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norræna ráðherranefndin |
E643926
|
entity |
| Predicate | officialNameInIcelandic |
P38525
|
FINISHED |
| Object | Norræna ráðherranefndin |
—
|
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: Norræna ráðherranefndin | Statement: [Norræna ráðherranefndin, officialNameInIcelandic, Norræna ráðherranefndin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialNameInIcelandic Context triple: [Norræna ráðherranefndin, officialNameInIcelandic, Norræna ráðherranefndin]
-
A.
IcelandicName
chosen
Indicates that the relationship specifies the Icelandic-language form of a name for an entity.
-
B.
officialNameInDanish
Indicates the officially recognized name of an entity when expressed in the Danish language.
-
C.
hasOfficialNameInFinnish
Indicates that an entity has a specific official name expressed in the Finnish language.
-
D.
officialNameInNorwegian
Indicates the officially recognized name of an entity when expressed in the Norwegian language.
-
E.
hasOfficialNameInEnglish
Indicates that an entity has an officially recognized name expressed in the English language.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 21, 2026, 7:57 p.m.