Triple
T24705217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Jasmund |
E611870
|
entity |
| Predicate | DanishCommander |
P157009
|
FINISHED |
| Object | Edouard Suenson |
—
|
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: Edouard Suenson | Statement: [Battle of Jasmund, DanishCommander, Edouard Suenson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DanishCommander Context triple: [Battle of Jasmund, DanishCommander, Edouard Suenson]
-
A.
hasDanishCommanderRank
Indicates that an entity holds or is assigned a military commander rank within the Danish armed forces.
-
B.
PrussianCommander
Indicates that an individual holds the position or role of a commander within the Prussian military forces.
-
C.
DutchCommander
Indicates that an entity serves as a military commander associated with the Netherlands.
-
D.
PolishCommander
Indicates that an entity serves as a military commander associated with Poland.
-
E.
ScottishCommander
Indicates that an entity serves as a military commander who is Scottish or associated with Scotland.
- F. None of above. chosen
Provenance (4 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410fc18808190b4e47d5a71d3a126 |
completed | May 1, 2026, 2:33 a.m. |
Created at: April 18, 2026, 3:23 a.m.