Triple
T8193333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visegrád |
E191366
|
entity |
| Predicate | distanceFromBudapest_km |
P7947
|
FINISHED |
| Object | approximately 40 |
—
|
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 40 | Statement: [Visegrád, distanceFromBudapest_km, approximately 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromBudapest_km Context triple: [Visegrád, distanceFromBudapest_km, approximately 40]
-
A.
distanceToBudapest_km
chosen
Indicates the physical distance, measured in kilometers, between a given location and Budapest.
-
B.
distanceFromBratislava_km
Indicates the distance, measured in kilometers, between a given entity’s location and the city of Bratislava.
-
C.
distanceFromPragueKmApprox
Indicates an approximate distance, measured in kilometers, between a given entity and the city of Prague.
-
D.
distanceToBasel_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Basel.
-
E.
distanceToBucharest
Indicates the physical distance between a given location and the city of Bucharest.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5c1d7aa48190adbbce88b3bed1a3 |
completed | March 31, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:42 p.m.