Triple
T32492314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paparoa Track |
E830420
|
entity |
| Predicate | bikingDirectionRule |
P174504
|
FINISHED |
| Object | mountain biking allowed in both directions |
—
|
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: mountain biking allowed in both directions | Statement: [Paparoa Track, bikingDirectionRule, mountain biking allowed in both directions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bikingDirectionRule Context triple: [Paparoa Track, bikingDirectionRule, mountain biking allowed in both directions]
-
A.
roadDirectionConvention
Indicates the customary rule in a place for which side of the road vehicles are expected to drive on.
-
B.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
C.
bikeway
Indicates that there is a designated path or route intended primarily for bicycle travel between locations.
-
D.
routeDirectionB
Indicates that one entity represents the direction or orientation of a route or path relative to another entity.
-
E.
trailOrientation
Indicates the directional alignment or facing direction of a trail relative to a reference frame or compass directions.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c407c3388190aa5eb09bd39022e9 |
completed | May 3, 2026, 3:41 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:59 a.m.