Triple
T30972960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Courtney Frerichs |
E789146
|
entity |
| Predicate | hasDistanceRange |
P175202
|
FINISHED |
| Object | 3000 metres |
—
|
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: 3000 metres | Statement: [Courtney Frerichs, hasDistanceRange, 3000 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistanceRange Context triple: [Courtney Frerichs, hasDistanceRange, 3000 metres]
-
A.
hasDistanceCategory
Indicates that one entity is associated with a qualitative or categorical classification of its distance relative to another entity or reference point.
-
B.
hasDistanceElement
chosen
Indicates that one entity includes or is associated with a component that specifies a distance value or measurement.
-
C.
designedForUseDistance
Indicates that something is intended or optimized to be used at a particular distance from the user or another object.
-
D.
hasRadiusRange
Indicates that there is a specified minimum and maximum radius within which the related entity or feature falls.
-
E.
isLongRange
Indicates that the relationship or action involves operating effectively over a large or extended distance.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: April 29, 2026, 8:55 p.m.