Triple
T31333054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryhill Basin |
E799085
|
entity |
| Predicate | basinFor |
P171251
|
FINISHED |
| Object | Forth and Clyde Canal traffic |
—
|
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: Forth and Clyde Canal traffic | Statement: [Maryhill Basin, basinFor, Forth and Clyde Canal traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basinFor Context triple: [Maryhill Basin, basinFor, Forth and Clyde Canal traffic]
-
A.
basin
Indicates a geographic area where surface water drains into a common outlet, such as a river, lake, or ocean.
-
B.
basinPartOf
Indicates that one basin is a component or subdivision of a larger basin or basin system.
-
C.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
-
D.
basinFeature
Indicates that one entity is a physical feature or component located within or forming part of a basin.
-
E.
locatedInBasin
Indicates that one geographical or hydrological feature lies within the drainage or catchment area of a specified basin.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f11ba548190b8ad25fafb07b62b |
completed | May 3, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69ea761848190acb31298e65b7892 |
completed | May 3, 2026, 1:02 a.m. |
Created at: April 29, 2026, 9:16 p.m.