Triple
T18058015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hansson |
E432090
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Hansen |
—
|
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: Hansen | Statement: [Hansson, hasVariant, Hansen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hansen Context triple: [Hansson, hasVariant, Hansen]
-
A.
Hansen
chosen
Hansen is a common Scandinavian-origin surname borne by numerous notable individuals across fields such as sports, politics, science, and the arts.
-
B.
Hahn
Hahn is a surname of German origin borne by various notable individuals across fields such as science, sports, and the arts.
-
C.
Reinholdt
Reinholdt is a masculine given name of Germanic origin, often associated with individuals from German-speaking regions.
-
D.
Hennenman
Hennenman is a small town in South Africa’s Free State province, situated within the Lejweleputswa District and known historically for its links to the regional mining and agricultural economy.
-
E.
Mortensen
Mortensen is a surname of Scandinavian origin borne by various notable individuals across fields such as economics, arts, and sports.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c1048c00819097c7dfbf76bb0987 |
completed | April 19, 2026, 11:48 a.m. |
Created at: April 10, 2026, 10:26 a.m.