Triple
T33896370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhyd Ddu |
E868920
|
entity |
| Predicate | hasFootpathRoute |
P98022
|
FINISHED |
| Object | Rhyd Ddu Path |
—
|
NE NERFINISHED |
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: Rhyd Ddu Path | Statement: [Rhyd Ddu, hasFootpathRoute, Rhyd Ddu Path]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFootpathRoute Context triple: [Rhyd Ddu, hasFootpathRoute, Rhyd Ddu Path]
-
A.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
B.
hasFootways
chosen
Indicates that something includes or is connected to designated footpaths or pedestrian walkways.
-
C.
hasWalkingRouteType
Indicates that an entity is associated with a specific type or category of walking route (e.g., trail, path, or walking itinerary).
-
D.
hasWalkingPathAround
Indicates that one entity has a walking path that encircles or runs around another entity.
-
E.
hasWalkingRouteConnection
Indicates that there is a walkable path or route directly connecting two locations.
- 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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: May 1, 2026, 1:48 a.m.