Triple
T28343267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truce of Vilnius (1656) |
E717872
|
entity |
| Predicate | opponentRedirectedAgainst |
P58158
|
FINISHED |
| Object | Sweden |
—
|
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: Sweden | Statement: [Truce of Vilnius (1656), opponentRedirectedAgainst, Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentRedirectedAgainst Context triple: [Truce of Vilnius (1656), opponentRedirectedAgainst, Sweden]
-
A.
opponentInCase
Indicates that two parties are on opposing sides in the same legal case or proceeding.
-
B.
opponentInScenario
chosen
Indicates that one entity is an adversary or rival of another within a specific scenario, context, or situation.
-
C.
intendedOpponents
Indicates that one entity is the target or adversary that another entity is meant or designed to oppose or confront.
-
D.
laterOpponent
Indicates that one entity becomes the opponent of another at a later time or stage, following an earlier phase or matchup.
-
E.
facedOpponent
Indicates that one entity directly confronted or competed against another as an opponent in a contest, conflict, or challenge.
- 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 12:41 a.m.