Triple
T12818914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgaria–Greece border |
E306474
|
entity |
| Predicate | EUInternalBorder |
P106527
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bulgaria–Greece border, EUInternalBorder, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EUInternalBorder Context triple: [Bulgaria–Greece border, EUInternalBorder, true]
-
A.
countryBorderDirection
Indicates the cardinal or relative direction in which one country lies in relation to the border it shares with another country.
-
B.
bordersVia
Indicates that two entities share a boundary or border that is specifically established, defined, or mediated through a particular intermediate feature, route, or medium.
-
C.
countryBorderFormsPartOf
Indicates that a specific border segment is part of the overall boundary between two countries.
-
D.
countryBorderType
Indicates the type or nature of the border relationship that exists between two countries.
-
E.
wasInnerGermanBorder
Indicates that a location or boundary segment functioned as part of the former inner German border separating East and West Germany.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e9e5a2481908921d097df541db8 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d964100f7481909a197396003d4a71 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d88be0481908c311f1e71b61e70 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:31 p.m.