Triple
T12890648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chepelare |
E308353
|
entity |
| Predicate | distanceToSmolyan |
P107290
|
FINISHED |
| Object | about 30 kilometres |
—
|
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: about 30 kilometres | Statement: [Chepelare, distanceToSmolyan, about 30 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSmolyan Context triple: [Chepelare, distanceToSmolyan, about 30 kilometres]
-
A.
distanceToPlovdiv
Indicates the spatial distance between a given entity and the city of Plovdiv.
-
B.
distanceFromBlagoevgrad
Indicates the physical distance between a given entity or location and the city of Blagoevgrad.
-
C.
distanceFromShumen
Indicates the spatial distance between a given entity and the location of Shumen.
-
D.
distanceFromSofia
Indicates the spatial distance between a given entity and the city of Sofia.
-
E.
distanceFromStaraZagoraApproximateKm
Indicates the approximate distance, measured in kilometers, between an entity and Stara Zagora.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97146d2208190be5ae26e51193b67 |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9713e45a88190acd346f066093550 |
completed | April 10, 2026, 9:53 p.m. |
Created at: April 9, 2026, 5:39 p.m.