Triple
T17278130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estonia–Russia border |
E419443
|
entity |
| Predicate | borderTreatySignedOn |
P126595
|
FINISHED |
| Object | 2005-05-18 |
—
|
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: 2005-05-18 | Statement: [Estonia–Russia border, borderTreatySignedOn, 2005-05-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTreatySignedOn Context triple: [Estonia–Russia border, borderTreatySignedOn, 2005-05-18]
-
A.
borderDemarcationTreaties
Indicates the existence of formal treaties that define, establish, or adjust the official boundary lines between two or more territories or jurisdictions.
-
B.
treatySignedFor
Indicates that a formal treaty has been signed on behalf of, or in representation of, a particular entity, cause, or subject.
-
C.
treatySignedWith
Indicates that a formal treaty or agreement has been officially signed between two parties.
-
D.
signedTreatyAt
Indicates that an entity formally entered into and endorsed a treaty at a specific location.
-
E.
treatySignedPlace
Indicates the location where a treaty was formally signed or concluded.
- F. None of above. chosen
Provenance (4 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e43327b048819095fbd93b2105533a |
completed | April 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e3874077948190acf5706cfe917d29 |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:40 a.m.