Triple
T27159034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guðjónsson |
E682605
|
entity |
| Predicate | followsIcelandicNamingTradition |
P88840
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Guðjónsson, followsIcelandicNamingTradition, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsIcelandicNamingTradition Context triple: [Guðjónsson, followsIcelandicNamingTradition, true]
-
A.
IcelandicName
Indicates that the relationship specifies the Icelandic-language form of a name for an entity.
-
B.
nameInOldNorse
Indicates that the given name is the form or equivalent of an entity’s name in the Old Norse language.
-
C.
isFixedFamilyNameInIceland
chosen
Indicates that a person’s family name is a fixed hereditary surname in Iceland, rather than a patronymic or matronymic name that changes each generation.
-
D.
followsIberianNamingCustom
Indicates that a person’s full name is structured according to Iberian naming customs, typically including given names followed by multiple family surnames in a culturally specific order.
-
E.
harTysktNamn
Indicates that an entity has a name in German.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 9:17 a.m.