Triple
T20404539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewenhaupt |
E500431
|
entity |
| Predicate | hasFamilyNameVariant |
P96655
|
FINISHED |
| Object | Lewenhaupt |
—
|
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: Lewenhaupt | Statement: [Lewenhaupt, hasFamilyNameVariant, Lewenhaupt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lewenhaupt Context triple: [Lewenhaupt, hasFamilyNameVariant, Lewenhaupt]
-
A.
Lewenhaupt
chosen
Lewenhaupt is a Swedish noble family name historically associated with prominent military and political figures in Sweden.
-
B.
Norrtull
Norrtull is a major traffic junction and historical city gate area in northern central Stockholm, Sweden.
-
C.
Stenbock
Stenbock is a Swedish noble family historically prominent in military and political affairs, notably producing figures such as general Magnus Stenbock.
-
D.
Sture
Sture is a Scandinavian male given name, particularly common in Sweden and historically borne by several notable figures.
-
E.
Tessin
Tessin is a region in southern Switzerland historically associated with Lepontic inscriptions and early Alpine Celtic culture.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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. |
Created at: April 16, 2026, 11:29 a.m.