Triple
T34859493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tripoint of Bulgaria–Greece–Turkey |
E1004825
|
entity |
| Predicate | nearVillageInBulgaria |
P182445
|
FINISHED |
| Object | Kapitan Andreevo |
—
|
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: Kapitan Andreevo | Statement: [tripoint of Bulgaria–Greece–Turkey, nearVillageInBulgaria, Kapitan Andreevo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearVillageInBulgaria Context triple: [tripoint of Bulgaria–Greece–Turkey, nearVillageInBulgaria, Kapitan Andreevo]
-
A.
nearVillageInTurkey
Indicates that one entity is located close to a village situated within the country of Turkey.
-
B.
nearVillageInGreece
Indicates that one entity is located close to a village situated within the country of Greece.
-
C.
distanceFromSofia
Indicates the spatial distance between a given entity and the city of Sofia.
-
D.
onlyBulgarianSettlementWithin
Indicates that a settlement is the only Bulgarian settlement located within a specified containing area or region.
-
E.
nearCityInNorthMacedonia
Indicates that one entity is located close to a specified city within the country of North Macedonia.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78d7211a48190bfb59c406f0bf12f |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c6014e08190864785a4fe3e8e73 |
completed | May 3, 2026, 5:56 p.m. |
Created at: May 3, 2026, 4 p.m.