Triple
T11151560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hansen |
E263797
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Hansson |
E432090
|
NE 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: Hansson | Statement: [Hansen, hasVariant, Hansson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hansson Context triple: [Hansen, hasVariant, Hansson]
-
A.
Hansson
chosen
Hansson is a common Swedish surname borne by numerous notable figures in politics, sports, and the arts.
-
B.
Hansi
Hansi is a historic town in the Hisar district of Haryana, India, known for its ancient forts and archaeological significance.
-
C.
Svante
Svante is the given name of Swedish geneticist Svante Pääbo, a Nobel Prize–winning pioneer in the field of paleogenomics.
-
D.
Söderblom
Söderblom is a Swedish surname most notably associated with Nathan Söderblom, the Nobel Peace Prize–winning Lutheran archbishop and ecumenical leader.
-
E.
Williamsson
Williamsson is a Scandinavian patronymic surname, likely meaning "son of William" and used as a variant of the more common form Williamson.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8719e74819095413abc6c79296c |
completed | April 9, 2026, 5:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4422ca62c81909a3a935fb7e28c34 |
completed | April 19, 2026, 2:47 a.m. |
Created at: April 8, 2026, 9:28 p.m.