Triple
T29339644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lukasson |
E744002
|
entity |
| Predicate | relatedToNameType |
P203129
|
FINISHED |
| Object | Scandinavian patronymic naming tradition |
—
|
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: Scandinavian patronymic naming tradition | Statement: [Lukasson, relatedToNameType, Scandinavian patronymic naming tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToNameType Context triple: [Lukasson, relatedToNameType, Scandinavian patronymic naming tradition]
-
A.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
C.
relatedToStructureType
Indicates that one entity has an association or connection with a particular type or category of structure.
-
D.
relatedToTerm
Indicates a general, non-specific relationship or association between one term and another.
-
E.
isRelatedName
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
- F. None of above. chosen
Provenance (4 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a012594c27081908c80f0e0e6010290 |
completed | May 11, 2026, 12:40 a.m. |
| PD | Predicate disambiguation | batch_6a01252350548190b1df9edc9e581e91 |
completed | May 11, 2026, 12:38 a.m. |
| PDg | Predicate description generation | batch_6a012593db3c8190b339c4db93f87e89 |
completed | May 11, 2026, 12:40 a.m. |
Created at: April 28, 2026, 1:33 p.m.