Triple
T6747132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huntingdon Road, Cambridge |
E154244
|
entity |
| Predicate | hasCycleInfrastructure |
P72720
|
FINISHED |
| Object | on-road cycle lanes |
—
|
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: on-road cycle lanes | Statement: [Huntingdon Road, Cambridge, hasCycleInfrastructure, on-road cycle lanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCycleInfrastructure Context triple: [Huntingdon Road, Cambridge, hasCycleInfrastructure, on-road cycle lanes]
-
A.
hasCycleAccess
Indicates that an entity is permitted to use or access a bicycle or cycling-related resource.
-
B.
hasCycleStorage
Indicates that a place or facility provides designated storage space for bicycles.
-
C.
includedInCycle
Indicates that an entity participates in and is part of a closed loop or recurring sequence within a system or structure.
-
D.
hasCycleLength
Indicates that an entity participates in or exhibits a cycle whose duration or size is specified by the associated length value.
-
E.
hasBridges
Indicates that one entity possesses, contains, or is characterized by one or more bridges connecting locations or components.
- 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_69c6880ef37881909268a5a7299b9293 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1b8a0f0819086b802983e8ffcb6 |
completed | March 27, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d14e18d481908aaac34897c650f1 |
completed | March 27, 2026, 6:49 p.m. |
Created at: March 27, 2026, 2:10 p.m.