Triple
T11037645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Polyanovka |
E260927
|
entity |
| Predicate | effectOnTsardomOfRussia |
P93970
|
FINISHED |
| Object | ended immediate threat to Moscow from Polish forces |
—
|
LITERAL FINISHED |
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: ended immediate threat to Moscow from Polish forces | Statement: [Treaty of Polyanovka, effectOnTsardomOfRussia, ended immediate threat to Moscow from Polish forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnTsardomOfRussia Context triple: [Treaty of Polyanovka, effectOnTsardomOfRussia, ended immediate threat to Moscow from Polish forces]
-
A.
tsarRussia
Indicates that the subject is the tsar (monarch) who rules over Russia.
-
B.
effectOnRussia
chosen
Indicates the impact or consequences that something has on Russia.
-
C.
countryDuringTsardom
Indicates that an entity functioned as a country or political unit during the historical period of tsardom.
-
D.
effectOnSmolensk
Indicates the impact or consequences that something has on Smolensk.
-
E.
effectOnAustria
Indicates the impact or influence that one entity, event, or action has on Austria.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797fd5fe081908af13835b18de7b8 |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:25 p.m.