Triple
T38209207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parrog |
E1009290
|
entity |
| Predicate | hasRecreationalRouteAccess |
P140677
|
FINISHED |
| Object | Pembrokeshire Coast Path |
E306479
|
NE 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: Pembrokeshire Coast Path | Statement: [Parrog, hasRecreationalRouteAccess, Pembrokeshire Coast Path]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecreationalRouteAccess Context triple: [Parrog, hasRecreationalRouteAccess, Pembrokeshire Coast Path]
-
A.
hasRecreationalRoute
Indicates that an entity is associated with or includes a route intended for recreational activities such as walking, cycling, or hiking.
-
B.
hasBikeTrailAccess
Indicates that an entity has direct access to, or is connected with, a bike trail suitable for cycling.
-
C.
hasScenicAccessTo
Indicates that one place or object provides a visually appealing or notable view of another place or object.
-
D.
hasHikingAccess
chosen
Indicates that one location or entity provides access or a connection to hiking trails or hiking areas.
-
E.
isRecreationalGateway
Indicates that something serves as an entry point or access hub for recreational activities or leisure experiences.
- F. None of above.
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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4193bf54208190ba0ba2fc12b5abca |
completed | June 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.