Triple
T31993167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lankaran |
E816921
|
entity |
| Predicate | involvedUnit (Russian Empire) |
P1063
|
FINISHED |
| Object | Caucasus Corps |
—
|
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: Caucasus Corps | Statement: [Battle of Lankaran, involvedUnit (Russian Empire), Caucasus Corps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedUnit (Russian Empire) Context triple: [Battle of Lankaran, involvedUnit (Russian Empire), Caucasus Corps]
-
A.
involvedUnitSoviet
Indicates that a Soviet military or organizational unit was involved in a particular event, operation, or action.
-
B.
involvedUnit
chosen
Indicates that a particular unit (such as a group, organization, or division) participates in, is associated with, or plays a role in the referenced event or activity.
-
C.
joinedRussianEmpire
Indicates that an entity became part of, or was incorporated into, the Russian Empire.
-
D.
involvedUnitAustriaHungary
Indicates that the unit or force specified was involved on behalf of Austria-Hungary in the referenced event or conflict.
-
E.
involvedUnitAustrian
Indicates that an Austrian military or organizational unit was involved as a participant in the referenced event or activity.
- 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_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 1, 2026, 12:13 a.m.