Triple
T28815768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croach Phádraig |
E727636
|
entity |
| Predicate | hasWaymarkedTrail |
P118683
|
FINISHED |
| Object | main pilgrim path from Murrisk |
—
|
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: main pilgrim path from Murrisk | Statement: [Croach Phádraig, hasWaymarkedTrail, main pilgrim path from Murrisk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaymarkedTrail Context triple: [Croach Phádraig, hasWaymarkedTrail, main pilgrim path from Murrisk]
-
A.
trailsMarkedBy
Indicates that a trail or path is designated or identified by specific markers, signs, or blazes placed along its route.
-
B.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
C.
hasTrailAccessPoint
Indicates that there is a specific access point or entrance connecting a location to a trail or pathway.
-
D.
hasApproachTrail
chosen
Indicates that there is a designated trail or path providing access or approach to a particular location or feature.
-
E.
hasNearbyTrail
Indicates that one entity is located close to or within a short distance of a trail.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 28, 2026, 6:32 a.m.