Triple
T24985802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rus'–Byzantine Wars |
E625302
|
entity |
| Predicate | primaryOpponentEntity |
P4675
|
FINISHED |
| Object | Kievan Rus' |
—
|
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: Kievan Rus' | Statement: [Rus'–Byzantine Wars, primaryOpponentEntity, Kievan Rus']
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOpponentEntity Context triple: [Rus'–Byzantine Wars, primaryOpponentEntity, Kievan Rus']
-
A.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
B.
secondaryOpponent
Indicates that an entity serves as an additional or backup opponent to a primary one in a given context or interaction.
-
C.
primaryOpponentsArgument
Indicates that the argument specified is the main or central argument presented by an opposing side in a debate or conflict.
-
D.
primaryEnemy
chosen
Indicates that one entity is the main or most significant adversary or opponent of another entity.
-
E.
primaryOpposingCountry
Indicates that one country is the main or principal adversary or opponent of another country in a conflict, rivalry, or opposition.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 18, 2026, 6:03 a.m.