Triple
T29618223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pocking |
E754921
|
entity |
| Predicate | distanceToAustrianBorder |
P202652
|
FINISHED |
| Object | approximately 10–15 km |
—
|
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 10–15 km | Statement: [Pocking, distanceToAustrianBorder, approximately 10–15 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToAustrianBorder Context triple: [Pocking, distanceToAustrianBorder, approximately 10–15 km]
-
A.
borderTownOnAustrianSide
Indicates that a town is located on the Austrian side of a border shared with another country.
-
B.
distanceToPolishBorder
Indicates the measured distance between a given location and the nearest point on the border of Poland.
-
C.
distanceToEisenstadt_km
Indicates the physical distance, measured in kilometers, between a given place and Eisenstadt.
-
D.
distanceFromVienna
Indicates the spatial distance between a given entity’s location and the city of Vienna.
-
E.
distanceToBulgarianBorder_km
Indicates the distance, measured in kilometers, from a given location to the nearest point on the Bulgarian national border.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a00a74c0564819081e1c4c29b9d0d15 |
completed | May 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_6a00a6a63ef48190a743c88534d9d672 |
completed | May 10, 2026, 3:39 p.m. |
| PDg | Predicate description generation | batch_6a00a74afb3c8190a274bf6681950aa3 |
completed | May 10, 2026, 3:42 p.m. |
Created at: April 28, 2026, 6:33 p.m.