Triple
T21215487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schaffer Farm mountain bike trails |
E522824
|
entity |
| Predicate | hasRidingStyle |
P114806
|
FINISHED |
| Object | flowy |
—
|
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: flowy | Statement: [Schaffer Farm mountain bike trails, hasRidingStyle, flowy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRidingStyle Context triple: [Schaffer Farm mountain bike trails, hasRidingStyle, flowy]
-
A.
rideStyle
chosen
Indicates the manner or characteristic way in which an entity rides or is ridden (e.g., in terms of technique, comfort, or behavior).
-
B.
hasDrivingStyle
Indicates the characteristic manner or pattern in which an entity typically drives.
-
C.
hasRidingAssociation
Indicates an association where one entity is related to another through the act or context of riding (e.g., serving as rider, mount, or riding partner).
-
D.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
-
E.
hasRacingSide
Indicates that an entity possesses or is associated with a side or aspect specifically dedicated to racing.
- 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73473870c8190a0f41f9c85567aa7 |
completed | April 21, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:40 p.m.