Triple
T31279821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strandzha region |
E797630
|
entity |
| Predicate | StrandzhaNatureParkLocatedIn |
P157505
|
FINISHED |
| Object | southeastern Bulgaria |
—
|
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: southeastern Bulgaria | Statement: [Strandzha region, StrandzhaNatureParkLocatedIn, southeastern Bulgaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: StrandzhaNatureParkLocatedIn Context triple: [Strandzha region, StrandzhaNatureParkLocatedIn, southeastern Bulgaria]
-
A.
distanceFromStaraZagoraApproximateKm
Indicates the approximate distance, measured in kilometers, between an entity and Stara Zagora.
-
B.
distanceFromSofia
Indicates the spatial distance between a given entity and the city of Sofia.
-
C.
localNatureSite
Indicates that a location is designated as a natural site of local significance or interest.
-
D.
distanceFromBlagoevgrad
Indicates the physical distance between a given entity or location and the city of Blagoevgrad.
-
E.
naturalAttractionOf
chosen
Indicates a relationship where one entity is a natural feature or site that draws interest, attention, or visitors from another entity.
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:13 p.m.