Triple
T31993145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lankaran |
E816921
|
entity |
| Predicate | combatantCommander (Russian Empire) |
P70146
|
FINISHED |
| Object | Pyotr Kotlyarevsky |
—
|
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: Pyotr Kotlyarevsky | Statement: [Battle of Lankaran, combatantCommander (Russian Empire), Pyotr Kotlyarevsky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantCommander (Russian Empire) Context triple: [Battle of Lankaran, combatantCommander (Russian Empire), Pyotr Kotlyarevsky]
-
A.
commanderSideRussia
chosen
Indicates that the commander is aligned with, fighting for, or acting on behalf of the Russian side in a conflict or military context.
-
B.
combatantCommander(Boer)
Indicates that the entity serves as a military leader or commander of combatants in a conflict.
-
C.
combatantRussianSide
Indicates that an entity participates as a combatant on the Russian side in a conflict or military engagement.
-
D.
combatant2Commander
Indicates that a combatant serves under the authority or command of a specific commander.
-
E.
commanderForSovietSide
Indicates that an entity serves as a military commander representing or leading forces on the Soviet side in a conflict or operation.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 12:13 a.m.