Triple
T1204132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Velence |
E25848
|
entity |
| Predicate | distanceToBudapest |
P7947
|
FINISHED |
| Object | about 50 kilometres southwest of Budapest |
—
|
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 50 kilometres southwest of Budapest | Statement: [Lake Velence, distanceToBudapest, about 50 kilometres southwest of Budapest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBudapest Context triple: [Lake Velence, distanceToBudapest, about 50 kilometres southwest of Budapest]
-
A.
distanceToBudapest_km
chosen
Indicates the physical distance, measured in kilometers, between a given location and Budapest.
-
B.
distanceToBerlin
Indicates the spatial distance between a given entity’s location and the city of Berlin.
-
C.
distanceToHelsinki_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Helsinki.
-
D.
distanceToIstanbulApproxKm
Indicates the approximate distance, measured in kilometers, between a given place and Istanbul.
-
E.
distanceToKraków_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Kraków.
- 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bdbf94188190991f63a84cc76b8a |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5ed2b88190aab992913957e1cf |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.