Triple
T3438777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | siege of Paris (845) |
E72518
|
entity |
| Predicate | commander |
P1061
|
FINISHED |
| Object | Ragnar |
E143680
|
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: Ragnar | Statement: [siege of Paris (845), commander, Ragnar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ragnar Context triple: [siege of Paris (845), commander, Ragnar]
-
A.
Ragnar
chosen
Ragnar is a masculine given name of Old Norse origin, historically associated with Viking-age Scandinavia and later borne by various notable figures.
-
B.
Gunnar
Gunnar is a masculine given name of Old Norse origin, commonly used in Scandinavian countries and associated with warriors or bold fighters.
-
C.
Tyr
Tyr is a Norse god associated primarily with law, justice, and heroic courage, famously known for sacrificing his hand to the wolf Fenrir.
-
D.
Raginmund
Raginmund is a Germanic personal name of early medieval origin that later evolved into forms such as the Spanish given name Ramón.
-
E.
Týr
Týr is a Norse god associated with law, justice, and heroic glory, best known for sacrificing his hand to bind the monstrous wolf Fenrir.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9f6de1481909b789f4b0e1113d3 |
completed | March 8, 2026, 6:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b35483d0488190b6a4bd2ed65f78d3 |
completed | March 13, 2026, 12:04 a.m. |
Created at: March 8, 2026, 3:16 p.m.