Triple
T20404564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewenhaupt |
E500431
|
entity |
| Predicate | hasFamilyNameCategory |
P17126
|
FINISHED |
| Object | Swedish-language surnames |
—
|
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: Swedish-language surnames | Statement: [Lewenhaupt, hasFamilyNameCategory, Swedish-language surnames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyNameCategory Context triple: [Lewenhaupt, hasFamilyNameCategory, Swedish-language surnames]
-
A.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
B.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
C.
hasFamilyNameElement
Indicates that an entity has a specific component or segment that forms part of its family name.
-
D.
familyNameCategory
chosen
Indicates that an entity is associated with a particular classification or grouping based on its family name.
-
E.
hasFamilyNameInLanguage
Indicates that an entity has a specific family name as expressed or written in a particular 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6799161c48190825eca3027d1aa51 |
completed | April 20, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:29 a.m.