Triple
T13803370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloemgracht |
E331695
|
entity |
| Predicate | hasCyclingUse |
P38724
|
FINISHED |
| Object | cycling along canal |
—
|
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: cycling along canal | Statement: [Bloemgracht, hasCyclingUse, cycling along canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCyclingUse Context triple: [Bloemgracht, hasCyclingUse, cycling along canal]
-
A.
bicycleUse
Indicates that an entity makes use of a bicycle for transportation, activity, or other purposes.
-
B.
hasRideCycle
Indicates that one entity is associated with, or participates in, a recurring sequence or cycle of rides or ride operations.
-
C.
hasBicycleFacilities
Indicates that appropriate bicycle-related infrastructure or amenities are available at or associated with the subject.
-
D.
bicyclesAllowed
chosen
Indicates that bicycles are permitted to use or access a particular route, area, or facility.
-
E.
hasBicyclePolicy
Indicates that there exists a specific policy or set of rules governing the use, storage, or management of bicycles in relation to the subject.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de026c36108190a7436034a730a261 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.