Triple
T15533353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Stolbovo |
E370278
|
entity |
| Predicate | signedOnDateOldStyle |
P439
|
FINISHED |
| Object | 1617-02-17 |
—
|
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: 1617-02-17 | Statement: [Treaty of Stolbovo, signedOnDateOldStyle, 1617-02-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedOnDateOldStyle Context triple: [Treaty of Stolbovo, signedOnDateOldStyle, 1617-02-17]
-
A.
signedOnSameDayAs
Indicates that two signing events occurred on the same calendar date, regardless of the specific time.
-
B.
signedOnAnniversaryOf
Indicates that an agreement or document was signed on the anniversary date of a specific prior event or reference point.
-
C.
signOnDate
Indicates the date on which an entity formally signs or enters into an agreement, contract, or system.
-
D.
agreementSignedAt
Indicates the specific time and/or place at which an agreement was formally signed.
-
E.
dateSigned
chosen
Indicates the specific date on which an agreement, document, or contract was formally signed.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0414877d88190804ee76566004e13 |
completed | April 16, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.