Triple
T31214784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kexholm |
E795840
|
entity |
| Predicate | mentionedInTreaty |
P75436
|
FINISHED |
| Object | Treaty of Stolbovo |
—
|
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: Treaty of Stolbovo | Statement: [Kexholm, mentionedInTreaty, Treaty of Stolbovo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionedInTreaty Context triple: [Kexholm, mentionedInTreaty, Treaty of Stolbovo]
-
A.
treatyMention
chosen
Indicates that a treaty is referenced or mentioned in relation to the associated entities or context.
-
B.
linkedToTreaty
Indicates that an entity has a formal connection or association with a specific treaty, such as being established by, governed by, or otherwise related to that treaty.
-
C.
relatedToTreaty
Indicates that there exists a connection, association, or relevance between an entity and a specific treaty or treaties.
-
D.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
E.
cededByTreaty
Indicates that control or ownership of one entity was formally transferred to another entity as a result of a treaty or formal agreement.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c2a62048190908fb27290410945 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:10 p.m.