Triple
T26714981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgaria–Turkey border |
E673524
|
entity |
| Predicate | languageInBorderRegion |
P77518
|
FINISHED |
| Object | Bulgarian |
—
|
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: Bulgarian | Statement: [Bulgaria–Turkey border, languageInBorderRegion, Bulgarian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageInBorderRegion Context triple: [Bulgaria–Turkey border, languageInBorderRegion, Bulgarian]
-
A.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
B.
languageAlongBorder
chosen
Indicates that a particular language is spoken or prevalent along the border between two regions or entities.
-
C.
languageArea
Indicates the geographic or cultural region in which a particular language is used or predominantly spoken.
-
D.
languageOfSurroundingCountry
Indicates that a language is the primary or commonly used language in the country surrounding a given place or region.
-
E.
alsoInLanguageRegion
Indicates that two or more entities are located within or associated with the same language-defined geographic region.
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 27, 2026, 3:37 a.m.