Triple
T11037644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Polyanovka |
E260927
|
entity |
| Predicate | effectOnPolishLithuanianCommonwealth |
P77475
|
FINISHED |
| Object | secured eastern frontier temporarily |
—
|
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: secured eastern frontier temporarily | Statement: [Treaty of Polyanovka, effectOnPolishLithuanianCommonwealth, secured eastern frontier temporarily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnPolishLithuanianCommonwealth Context triple: [Treaty of Polyanovka, effectOnPolishLithuanianCommonwealth, secured eastern frontier temporarily]
-
A.
effectOnPolity
chosen
Indicates the impact or consequence that one entity, event, or action has on a political body or governing organization.
-
B.
polishUnit
Indicates that one entity performs the action of polishing or refining another entity, typically improving its surface, appearance, or quality.
-
C.
effectOnAustria
Indicates the impact or influence that one entity, event, or action has on Austria.
-
D.
PolishObjective
Indicates that an entity is the target or goal of a polishing action or process.
-
E.
effectOfUnion
Indicates the outcome or consequence that results from forming a union or combining entities.
- 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.