Triple
T27392322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kouvola |
E691571
|
entity |
| Predicate | drivingTimeToHelsinkiApprox |
P162380
|
FINISHED |
| Object | 1.5 hours |
—
|
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: 1.5 hours | Statement: [Kouvola, drivingTimeToHelsinkiApprox, 1.5 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivingTimeToHelsinkiApprox Context triple: [Kouvola, drivingTimeToHelsinkiApprox, 1.5 hours]
-
A.
distanceToHelsinki_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Helsinki.
-
B.
distanceToTurku
Indicates the spatial distance between a given entity’s location and the city of Turku.
-
C.
distanceToLappeenranta_km
Indicates the physical distance, measured in kilometers, between an entity and the city of Lappeenranta.
-
D.
distanceToPori
Indicates the measured distance from a given entity or location to Pori.
-
E.
distanceToOulu_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Oulu.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cae21408190836baa6f4a1b52a2 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 12:26 p.m.