Triple
T25738753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slivnitsa Municipality |
E648154
|
entity |
| Predicate | borderingHigherLevelRegion |
P10768
|
FINISHED |
| Object | Sofia Province |
—
|
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 Province | Statement: [Slivnitsa Municipality, borderingHigherLevelRegion, Sofia Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingHigherLevelRegion Context triple: [Slivnitsa Municipality, borderingHigherLevelRegion, Sofia Province]
-
A.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
B.
borderRegionOf
chosen
Indicates that one region lies along, touches, or forms part of the boundary of another region.
-
C.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
crossBorderRegion
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
E.
borderRegionsInclude
Indicates that the specified border area encompasses or contains the referenced regions within its boundaries.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 22, 2026, 3:38 a.m.