Triple
T33419298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minffordd Path |
E855802
|
entity |
| Predicate | approximateRoundDistance |
P198422
|
FINISHED |
| Object | 10 km |
—
|
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: 10 km | Statement: [Minffordd Path, approximateRoundDistance, 10 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateRoundDistance Context triple: [Minffordd Path, approximateRoundDistance, 10 km]
-
A.
approximateDistanceFrom
Indicates an estimated or rough measure of how far one entity is from another.
-
B.
approximateRadius
Indicates that one entity specifies or provides an estimated value for the radius of another entity.
-
C.
approximateDistanceUnit
Indicates that the distance value is expressed in an approximate or non-exact unit of measurement.
-
D.
roundOf
Indicates that one event, match, or game occurs as a specific stage or phase within a larger competition or tournament.
-
E.
hasApproximateDistanceScale
Indicates that one entity is related to another by a distance measure that is approximate or estimated rather than exact.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
| PDg | Predicate description generation | batch_69fee25c7c548190a2c6e50074a33da4 |
completed | May 9, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:36 a.m.