Triple
T8769863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mynämäki |
E208429
|
entity |
| Predicate | distanceFromTurku |
P34271
|
FINISHED |
| Object | approximately 40 km northwest of Turku |
—
|
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 km northwest of Turku | Statement: [Mynämäki, distanceFromTurku, approximately 40 km northwest of Turku]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromTurku Context triple: [Mynämäki, distanceFromTurku, approximately 40 km northwest of Turku]
-
A.
distanceToTurku
chosen
Indicates the spatial distance between a given entity’s location and the city of Turku.
-
B.
distanceToHelsinki_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Helsinki.
-
C.
distanceToLappeenranta_km
Indicates the physical distance, measured in kilometers, between an entity and the city of Lappeenranta.
-
D.
distanceFromUppsala_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Uppsala.
-
E.
distanceFromTallinn
Indicates the measured distance between a given place or object and the city of Tallinn.
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5eedc7188190a67d959b9af53837 |
completed | March 31, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:41 p.m.