Triple
T26044571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ardoch Burn |
E647790
|
entity |
| Predicate | hasNotableSiteAlongCourse |
P115563
|
FINISHED |
| Object | Doune Castle |
—
|
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: Doune Castle | Statement: [Ardoch Burn, hasNotableSiteAlongCourse, Doune Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSiteAlongCourse Context triple: [Ardoch Burn, hasNotableSiteAlongCourse, Doune Castle]
-
A.
hasNotableFeatureAlongCourse
chosen
Indicates that something possesses a notable or distinguishing feature at some point along its course or path.
-
B.
hasMunicipalityAlongCourse
Indicates that a watercourse passes through or alongside a given municipality along its path.
-
C.
hasNotableScenicSpot
Indicates that an entity possesses or is associated with a particularly remarkable or well-known scenic location.
-
D.
hasNotableClimbingRoute
Indicates that an entity is associated with a climbing route that is recognized as significant, famous, or otherwise noteworthy.
-
E.
crossCountryCourseNotableFor
Indicates that a cross-country course is distinguished or recognized for a particular feature, quality, or characteristic.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 22, 2026, 9:09 a.m.