Triple
T7191139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regent Street, Cambridge |
E167692
|
entity |
| Predicate | hasCyclingFacilities |
P1709
|
FINISHED |
| Object | used by cyclists |
—
|
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: used by cyclists | Statement: [Regent Street, Cambridge, hasCyclingFacilities, used by cyclists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCyclingFacilities Context triple: [Regent Street, Cambridge, hasCyclingFacilities, used by cyclists]
-
A.
hasBicycleFacilities
chosen
Indicates that appropriate bicycle-related infrastructure or amenities are available at or associated with the subject.
-
B.
hasRideCycle
Indicates that one entity is associated with, or participates in, a recurring sequence or cycle of rides or ride operations.
-
C.
cyclingVenue
Indicates a location or facility where cycling activities, such as training, racing, or recreational riding, take place.
-
D.
bicycleUse
Indicates that an entity makes use of a bicycle for transportation, activity, or other purposes.
-
E.
bicyclesAllowed
Indicates that bicycles are permitted to use or access a particular route, area, or facility.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e90087208190a65e49ae0e8a7cbf |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:50 p.m.