Triple
T25593815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lake Peipus |
E641592
|
entity |
| Predicate | hasMainCommanderForNovgorod |
P1197
|
FINISHED |
| Object | Alexander Nevsky |
—
|
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: Alexander Nevsky | Statement: [Battle of Lake Peipus, hasMainCommanderForNovgorod, Alexander Nevsky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCommanderForNovgorod Context triple: [Battle of Lake Peipus, hasMainCommanderForNovgorod, Alexander Nevsky]
-
A.
hasCommander
chosen
Indicates that one entity serves as the commanding officer or leader of another entity.
-
B.
MongolianCommander
Indicates that an individual holds a commanding or leadership role within a Mongolian military or armed force context.
-
C.
commanderOfWallachia
Indicates that one entity serves as the military commander responsible for the forces or defense of Wallachia.
-
D.
reignAsGrandPrinceOfMoscowFrom
Indicates that a person held the position of Grand Prince of Moscow starting from a specified time.
-
E.
PolishCommander
Indicates that an entity serves as a military commander associated with Poland.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 21, 2026, 4:26 p.m.