Triple
T28045817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montenegro–Kosovo border |
E708675
|
entity |
| Predicate | borderAgreementSigned |
P126595
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Montenegro–Kosovo border, borderAgreementSigned, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderAgreementSigned Context triple: [Montenegro–Kosovo border, borderAgreementSigned, 2015]
-
A.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
-
B.
tradeAgreementSigned
Indicates that a formal trade agreement has been officially concluded and signed between the involved parties.
-
C.
agreementSignedBy
Indicates that a particular agreement has been formally signed or executed by a specified party.
-
D.
borderTreatySignedOn
chosen
Indicates that a formal agreement establishing or modifying a border between entities was signed on a specific date.
-
E.
rightsAgreementSignedWith
Indicates that a formal rights agreement has been executed and signed between two parties.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 27, 2026, 8:29 p.m.