Triple
T29305372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam-Noord |
E743076
|
entity |
| Predicate | bikeInfrastructure |
P1709
|
FINISHED |
| Object | extensive cycling paths connecting to central Amsterdam |
—
|
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: extensive cycling paths connecting to central Amsterdam | Statement: [Amsterdam-Noord, bikeInfrastructure, extensive cycling paths connecting to central Amsterdam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bikeInfrastructure Context triple: [Amsterdam-Noord, bikeInfrastructure, extensive cycling paths connecting to central Amsterdam]
-
A.
hasBicycleFacilities
chosen
Indicates that appropriate bicycle-related infrastructure or amenities are available at or associated with the subject.
-
B.
bikeway
Indicates that there is a designated path or route intended primarily for bicycle travel between locations.
-
C.
hasBikeInfrastructureOpeningYear
Indicates the year in which a piece of bike-related infrastructure was first opened or became operational.
-
D.
bicycleUse
Indicates that an entity makes use of a bicycle for transportation, activity, or other purposes.
-
E.
hasBikewayTerminus
Indicates that a bikeway ends, terminates, or has its final point at the referenced location or entity.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665a631948190bb1a8cbb5df633ae |
completed | May 2, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:13 p.m.