Triple
T29465778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etikhove |
E747373
|
entity |
| Predicate | roadCyclingFeature |
P1777
|
FINISHED |
| Object | Etikhovestraat climb |
—
|
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: Etikhovestraat climb | Statement: [Etikhove, roadCyclingFeature, Etikhovestraat climb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadCyclingFeature Context triple: [Etikhove, roadCyclingFeature, Etikhovestraat climb]
-
A.
roadFeature
chosen
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
B.
bikeway
Indicates that there is a designated path or route intended primarily for bicycle travel between locations.
-
C.
cyclingRoadRaceVenue
Indicates that a location serves as the venue where a cycling road race event takes place.
-
D.
raceRoute
Indicates that one entity serves as the course or path along which a race or competitive event is conducted for another entity.
-
E.
isMountainRoad
Indicates that a given road is classified as a mountain road, typically traversing or situated within mountainous terrain.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66ba7afcc8190a98cfe4f88ab7bc7 |
completed | May 2, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:52 p.m.