Triple
T22133643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ii |
E546968
|
entity |
| Predicate | distanceToOulu |
P147119
|
FINISHED |
| Object | approximately 35 kilometres |
—
|
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 35 kilometres | Statement: [Ii, distanceToOulu, approximately 35 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToOulu Context triple: [Ii, distanceToOulu, approximately 35 kilometres]
-
A.
distanceToOulu_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Oulu.
-
B.
distanceToTurku
Indicates the spatial distance between a given entity’s location and the city of Turku.
-
C.
distanceToHelsinki_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Helsinki.
-
D.
distanceToLappeenranta_km
Indicates the physical distance, measured in kilometers, between an entity and the city of Lappeenranta.
-
E.
distanceToTampere
Indicates the measured or calculated distance between a given entity’s location and the city of Tampere.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129b81d5c819085fd18bf3ae28333 |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:32 p.m.