Triple
T26610662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American harness racing |
E667911
|
entity |
| Predicate | hasCommonDistance |
P195995
|
FINISHED |
| Object | one mile |
—
|
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: one mile | Statement: [North American harness racing, hasCommonDistance, one mile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonDistance Context triple: [North American harness racing, hasCommonDistance, one mile]
-
A.
hasNearbyCommon
Indicates that two entities share at least one common element, feature, or connection that is located within a specified nearby distance or vicinity.
-
B.
hasDistanceElement
Indicates that one entity includes or is associated with a component that specifies a distance value or measurement.
-
C.
hasMultipleDistances
Indicates that a relationship or connection involves more than one distinct distance or separation value between the related entities.
-
D.
hasDistanceReference
Indicates that a distance value is specified relative to a particular reference point, scale, or standard.
-
E.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
- 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
| PDg | Predicate description generation | batch_69fe00d8d8248190a63c12aa2c2f7c0c |
completed | May 8, 2026, 3:27 p.m. |
Created at: April 27, 2026, 2:16 a.m.