Triple
T20138065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leppneeme |
E491078
|
entity |
| Predicate | distanceToTallinn |
P66356
|
FINISHED |
| Object | approximately 15 km northeast |
—
|
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 northeast | Statement: [Leppneeme, distanceToTallinn, approximately 15 km northeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToTallinn Context triple: [Leppneeme, distanceToTallinn, approximately 15 km northeast]
-
A.
distanceFromTallinn
chosen
Indicates the measured distance between a given place or object and the city of Tallinn.
-
B.
distanceToHelsinki_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Helsinki.
-
C.
distanceToTurku
Indicates the spatial distance between a given entity’s location and the city of Turku.
-
D.
distanceFromRiga
Indicates the spatial distance between a given entity and the city of Riga.
-
E.
distanceFromVilnius
Indicates the spatial distance between an entity and the city of Vilnius.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6676879f48190a59da04393d2a8cc |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:32 p.m.