Triple
T26714950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgaria–Turkey border |
E673524
|
entity |
| Predicate | hasCapitalOnBorderingCountry |
P179905
|
FINISHED |
| Object | Sofia |
—
|
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: Sofia | Statement: [Bulgaria–Turkey border, hasCapitalOnBorderingCountry, Sofia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalOnBorderingCountry Context triple: [Bulgaria–Turkey border, hasCapitalOnBorderingCountry, Sofia]
-
A.
hasBorderWithNonSovereignEntity
Indicates that one entity shares a land or maritime border with a political or territorial unit that is not fully sovereign.
-
B.
borderingCountryOfState
Indicates that one country shares a land or maritime boundary directly with the specified state.
-
C.
countryBordering
Indicates that one country shares a land or maritime boundary directly with another country.
-
D.
sharesInternationalBorderWith
Indicates that two geographic or political entities have a common boundary that is recognized as an international border.
-
E.
borderingPoliticalEntityType
Indicates that one political entity is adjacent to and shares a boundary with another political entity of a specified type.
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f72920c6208190aa4aba6cb6193109 |
completed | May 3, 2026, 10:53 a.m. |
Created at: April 27, 2026, 3:37 a.m.