Triple
T24548058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budrio |
E607280
|
entity |
| Predicate | distanceToBologna |
P156279
|
FINISHED |
| Object | approximately 15 km east |
—
|
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: approximately 15 km east | Statement: [Budrio, distanceToBologna, approximately 15 km east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBologna Context triple: [Budrio, distanceToBologna, approximately 15 km east]
-
A.
distanceToBergamo
Indicates the spatial distance between a given entity and the location of Bergamo.
-
B.
distanceFromMilan
Indicates the spatial distance between a given entity and the city of Milan.
-
C.
distanceToPadua
Indicates the measured distance between a given entity’s location and the city of Padua.
-
D.
distanceToBari
Indicates the measured distance between a given entity (such as a place or object) and the location of Bari.
-
E.
distanceToTurin
Indicates the spatial distance between a given entity or location and the city of Turin.
- 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8cb6dc081909bf37123d82ed2c9 |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:27 a.m.