Triple
T7651784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulf Lundell |
E173270
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Ulf |
E473809
|
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: Ulf | Statement: [Ulf Lundell, givenName, Ulf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ulf Context triple: [Ulf Lundell, givenName, Ulf]
-
A.
Ulf
chosen
Ulf is a masculine given name of Germanic origin, commonly used in German and Scandinavian countries.
-
B.
Ivar
Ivar is a masculine given name of Old Norse origin, traditionally used in Scandinavian countries.
-
C.
Ingvar
Ingvar is a Scandinavian given name of Old Norse origin, historically associated with Viking-age figures and meaning roughly "Ing’s warrior" or "warrior of the god Ing."
-
D.
Anund
Anund was a Viking chieftain who served as one of the leaders of the Great Heathen Army during its campaigns in England in the late 9th century.
-
E.
Halvdan
Halvdan is a masculine given name of Scandinavian origin, historically borne by several notable Norwegian figures.
- 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_69c6995473348190a4f41d110d619a18 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c701770ac881909452348c9547ab47 |
completed | March 27, 2026, 10:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8ac925a6c8190aa7a4fe4f580d14f |
completed | March 29, 2026, 4:37 a.m. |
Created at: March 27, 2026, 3:58 p.m.