Triple
T25132560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bervie Water |
E629563
|
entity |
| Predicate | hasCourseThrough |
P177993
|
FINISHED |
| Object | Aberdeenshire countryside |
—
|
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: Aberdeenshire countryside | Statement: [Bervie Water, hasCourseThrough, Aberdeenshire countryside]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCourseThrough Context triple: [Bervie Water, hasCourseThrough, Aberdeenshire countryside]
-
A.
hasTypicalCourse
Indicates that there is a characteristic or commonly observed progression, sequence, or development pattern associated with the subject.
-
B.
hasJumpCourse
Indicates that an entity is associated with or offers a course specifically focused on jumping activities or skills.
-
C.
hasCoursePattern
Indicates that an entity follows, is associated with, or is defined by a particular course structure or pattern.
-
D.
hasSisterCourse
Indicates that one course is related to another as a sister course, typically sharing similar content, level, or structure within the same curriculum or program.
-
E.
hasMultipleCourses
Indicates that an entity is associated with more than one course within the given context.
- F. None of above. chosen
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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f707f380388190954b79d52a321921 |
completed | May 3, 2026, 8:31 a.m. |
Created at: April 18, 2026, 6:28 a.m.