Triple
T17199085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frisian Eleven Cities |
E417428
|
entity |
| Predicate | tourDistanceApproxKm |
P126702
|
FINISHED |
| Object | 200 |
—
|
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: 200 | Statement: [Frisian Eleven Cities, tourDistanceApproxKm, 200]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourDistanceApproxKm Context triple: [Frisian Eleven Cities, tourDistanceApproxKm, 200]
-
A.
trackLengthApproxKm
Indicates that one entity has an approximate track length, measured in kilometers, associated with it.
-
B.
lengthInKm
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
-
C.
range_km
Indicates the maximum distance, measured in kilometers, over which something can operate, travel, or be effective.
-
D.
approximateDistanceKm
Indicates the estimated distance between two entities measured in kilometers, typically with some degree of inaccuracy or approximation.
-
E.
trailDistanceApprox
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42daca29081909837494d8d516634 |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:38 a.m.