Triple
T11639152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guy Hedlund |
E276611
|
entity |
| Predicate | family name |
P18
|
FINISHED |
| Object | Hedlund |
E374396
|
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: Hedlund | Statement: [Guy Hedlund, family name, Hedlund]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hedlund Context triple: [Guy Hedlund, family name, Hedlund]
-
A.
Hedlund
chosen
Hedlund is a surname most notably associated with American actor Garrett Hedlund, known for roles in films like "Tron: Legacy" and "Friday Night Lights."
-
B.
Hellerud
Hellerud is a residential neighborhood in Oslo, Norway, known for its hillside location and proximity to green areas and public transport.
-
C.
Hedman
Hedman is a Swedish surname most prominently associated with Victor Hedman, an elite NHL defenseman for the Tampa Bay Lightning.
-
D.
Linderud
Linderud is a residential neighborhood in Oslo, Norway, known for its apartment blocks, shopping center, and access to public transportation.
-
E.
Edlund
Edlund is a surname of Scandinavian origin borne by various notable individuals in fields such as film, science, and the arts.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25e90c08190b7fb73939a2be3d7 |
completed | April 10, 2026, 7:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ee87d006e881908e008ffa17502d47 |
completed | April 26, 2026, 9:46 p.m. |
Created at: April 8, 2026, 9:39 p.m.