Triple
T37037361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torben Hansen |
E916680
|
entity |
| Predicate | associatedWithSurnameEntry |
P49952
|
FINISHED |
| Object | Hansen (surname) |
—
|
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: Hansen (surname) | Statement: [Torben Hansen, associatedWithSurnameEntry, Hansen (surname)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSurnameEntry Context triple: [Torben Hansen, associatedWithSurnameEntry, Hansen (surname)]
-
A.
associatedSurname
chosen
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
-
B.
surnameAssociatedWithField
Indicates that a particular surname is commonly linked or connected to a specific professional, academic, or activity-related field.
-
C.
associatedName
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
D.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
-
E.
correspondsToSurname
Indicates that one entity is the surname or family name associated with, matching, or representing the other entity.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.