Triple
T27643944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kosovo–North Macedonia border |
E696657
|
entity |
| Predicate | borderAgreementYear |
P117579
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Kosovo–North Macedonia border, borderAgreementYear, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderAgreementYear Context triple: [Kosovo–North Macedonia border, borderAgreementYear, 2009]
-
A.
borderTreatySignedOn
Indicates that a formal agreement establishing or modifying a border between entities was signed on a specific date.
-
B.
agreementYear
chosen
Indicates the calendar year in which an agreement between the related entities was made, signed, or came into effect.
-
C.
becameInternationalBorderInYear
Indicates that a boundary between entities started functioning as an international border in the specified year.
-
D.
borderDemarcationTreaties
Indicates the existence of formal treaties that define, establish, or adjust the official boundary lines between two or more territories or jurisdictions.
-
E.
treatySettlementYear
Indicates the year in which a treaty was formally settled or concluded.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 27, 2026, 2:28 p.m.