Triple
T30327937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Dam Bridge 100 cycling tour |
E771390
|
entity |
| Predicate | distanceOption |
P196666
|
FINISHED |
| Object | 100-mile route |
—
|
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: 100-mile route | Statement: [Big Dam Bridge 100 cycling tour, distanceOption, 100-mile route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceOption Context triple: [Big Dam Bridge 100 cycling tour, distanceOption, 100-mile route]
-
A.
distanceProvidedBy
Indicates that a specific distance value is supplied or made available by a particular source or provider.
-
B.
hasDistanceOption
chosen
Indicates that there is an available choice or configuration related to distance between entities or for an action.
-
C.
distanceMeasurementMethod
Indicates the method or technique used to determine or measure the distance between entities.
-
D.
distanceCharacteristic
Indicates a relationship where an entity is described or constrained by some property or measure of distance (e.g., range, spacing, or separation).
-
E.
distance
Indicates the spatial separation or length between two points, objects, or locations.
- 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a011e5a419081908d06a07b395ebd97 |
completed | May 11, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_6a011de119048190b27d361cffabc228 |
completed | May 11, 2026, 12:08 a.m. |
Created at: April 29, 2026, 7:53 p.m.