Triple
T10429074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of 1716 |
E245860
|
entity |
| Predicate | commander |
P1061
|
FINISHED |
| Object | Tordenskjold |
E253918
|
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: Tordenskjold | Statement: [Siege of 1716, commander, Tordenskjold]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tordenskjold Context triple: [Siege of 1716, commander, Tordenskjold]
-
A.
Tordenskjold
chosen
Tordenskjold was a famed early 18th-century Norwegian-Danish naval hero and officer known for his daring exploits against Sweden during the Great Northern War.
-
B.
Haraldsen
Haraldsen is a Norwegian surname most notably borne by Queen Sonja of Norway before her marriage into the royal family.
-
C.
Halvdan
Halvdan is a masculine given name of Scandinavian origin, historically borne by several notable Norwegian figures.
-
D.
Norseman
Norseman is a remote gold-mining town in Western Australia's outback, known as a gateway to the Nullarbor Plain and the eastern states.
-
E.
Ivar
Ivar is a masculine given name of Old Norse origin, traditionally used in Scandinavian countries.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea4b4b5881908ae23f8efeea482b |
completed | April 7, 2026, 11:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d87eb068bc8190be9c7c916850278e |
completed | April 10, 2026, 4:38 a.m. |
Created at: April 6, 2026, 12:13 p.m.