Triple
T37958041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Louis Stevenson Trail |
E946920
|
entity |
| Predicate | isWaymarkedAs |
P47567
|
FINISHED |
| Object | GR 70 |
—
|
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: GR 70 | Statement: [Robert Louis Stevenson Trail, isWaymarkedAs, GR 70]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWaymarkedAs Context triple: [Robert Louis Stevenson Trail, isWaymarkedAs, GR 70]
-
A.
waymarkingStatus
Indicates the current state or condition of a waymarking process, such as whether a location or route has been identified, recorded, approved, or otherwise classified in a waymarking system.
-
B.
hasTouristSignage
Indicates that there is official signage present to guide or inform tourists about a place, route, or attraction.
-
C.
signpostFeature
Indicates that one entity serves as a signpost-related feature or element associated with another entity.
-
D.
trailsMarkedBy
chosen
Indicates that a trail or path is designated or identified by specific markers, signs, or blazes placed along its route.
-
E.
isLandmarkFor
Indicates that one entity serves as a notable or significant reference point or attraction for another entity, such as a place, route, or area.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.