Triple
T13850384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulf Nilsson |
E332920
|
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 Nilsson, givenName, Ulf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ulf Context triple: [Ulf Nilsson, 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.
Ulf Jarl
Ulf Jarl was an influential early 11th-century Danish nobleman and military leader, brother-in-law to King Cnut the Great and father of the later Danish king Sweyn II.
-
D.
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."
-
E.
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.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02d8fb788190baef7537be2baecb |
completed | April 14, 2026, 9:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c0f35ba48190b8b071679251233f |
completed | May 3, 2026, 9:41 p.m. |
Created at: April 9, 2026, 10:14 p.m.