Triple
T31993162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lankaran |
E816921
|
entity |
| Predicate | countryAtTime (attacker) |
P878
|
FINISHED |
| Object | Russian Empire |
—
|
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: Russian Empire | Statement: [Battle of Lankaran, countryAtTime (attacker), Russian Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryAtTime (attacker) Context triple: [Battle of Lankaran, countryAtTime (attacker), Russian Empire]
-
A.
countryAttacker
Indicates that one country is the aggressor or initiator of an attack against another country.
-
B.
countryAtTheTime
chosen
Indicates that an entity is associated with a specific country as it existed at a particular point in time.
-
C.
attackCountry
Indicates that one country initiates a hostile or military action against another country.
-
D.
countryOfOriginOfAttackers
Indicates the country from which the attackers originated or are associated in the context of an attack.
-
E.
countryOfDefender
Indicates the country to which the defending party or entity in a conflict, dispute, or legal case belongs.
- 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_6a0019b0e9fc81909494320f05e81742 |
completed | May 10, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a00193379e0819096d1985686ce10e3 |
completed | May 10, 2026, 5:35 a.m. |
Created at: May 1, 2026, 12:13 a.m.