Triple
T16129851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roose Bolton |
E391365
|
entity |
| Predicate | culture |
P1114
|
FINISHED |
| Object | Northmen |
E203461
|
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: Northmen | Statement: [Roose Bolton, culture, Northmen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Northmen Context triple: [Roose Bolton, culture, Northmen]
-
A.
Vikes
Vikes is a common shortened nickname for the Minnesota Vikings, the professional American football team based in Minneapolis.
-
B.
Vikes
Vikes is the nickname and athletic brand for the University of Victoria’s varsity sports teams in Canada.
-
C.
Varangians
chosen
The Varangians were Norse seafarers, traders, and warriors—primarily from what is now Sweden—who traveled and settled along the river routes of Eastern Europe, playing a key role in the formation of early Rus' states and serving as elite mercenaries such as the Byzantine Varangian Guard.
-
D.
Viking
"Viking" is a Russian historical epic film depicting the rise of Prince Vladimir and the Christianization of Kievan Rus.
-
E.
Viking
The Viking is a Norse seafaring warrior figure commonly used as a symbol of strength and bravery, including as a school mascot.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e202075860819088d27d921609a6ce |
completed | April 17, 2026, 9:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff2aff07c8190bf693f652e2a2808 |
completed | May 10, 2026, 2:51 a.m. |
Created at: April 10, 2026, 5:01 a.m.