Triple
T23961703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Als |
E603945
|
entity |
| Predicate | commanderDenmark |
P1061
|
FINISHED |
| Object | General Peter Christian Bjørnskov |
—
|
NE NERFINISHED |
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: General Peter Christian Bjørnskov | Statement: [Battle of Als, commanderDenmark, General Peter Christian Bjørnskov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderDenmark Context triple: [Battle of Als, commanderDenmark, General Peter Christian Bjørnskov]
-
A.
hasDanishCommanderRank
Indicates that an entity holds or is assigned a military commander rank within the Danish armed forces.
-
B.
commander
chosen
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
C.
DutchCommander
Indicates that an entity serves as a military commander associated with the Netherlands.
-
D.
commanderNationality
Indicates the national affiliation or citizenship of a given commander.
-
E.
combatantCommanderSweden
Indicates that the referenced entity serves as a commander of Swedish combatant forces in a conflict or military context.
- F. None of above.
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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0dac8e081908286e8d8d30784ee |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:23 p.m.