Triple
T16540125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl Asmund Rudolphi |
E401798
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Asmund |
E831919
|
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: Asmund | Statement: [Karl Asmund Rudolphi, givenName, Asmund]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Asmund Context triple: [Karl Asmund Rudolphi, givenName, Asmund]
-
A.
Aasmund
chosen
Aasmund is a masculine given name of Norwegian origin, notably borne by the 19th-century writer and journalist Aasmund Olavsson Vinje.
-
B.
Svein
Svein is a masculine given name of Old Norse origin, commonly used in Scandinavian countries.
-
C.
Halvdan
Halvdan is a masculine given name of Scandinavian origin, historically borne by several notable Norwegian figures.
-
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.
Orpund
Orpund is a municipality in the canton of Bern in Switzerland, situated near the city of Biel/Bienne.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3455bd43c8190b01560d4af55a9e0 |
completed | April 18, 2026, 8:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0067ae169c81909a123b7dfe3fd906 |
completed | May 10, 2026, 11:10 a.m. |
Created at: April 10, 2026, 5:15 a.m.