Triple
T31333045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryhill Basin |
E799085
|
entity |
| Predicate | historicNetwork |
P199442
|
FINISHED |
| Object | Forth and Clyde Canal |
—
|
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: Forth and Clyde Canal | Statement: [Maryhill Basin, historicNetwork, Forth and Clyde Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicNetwork Context triple: [Maryhill Basin, historicNetwork, Forth and Clyde Canal]
-
A.
historicCore
Indicates that something is part of, located within, or associated with the original historic center or oldest developed area of a place.
-
B.
historicFor
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
C.
historicActivity
Indicates that an entity engaged in an activity or event of historical significance in the past.
-
D.
architectureHistory
Indicates a historical or developmental relationship between an entity and its architectural evolution, style, or significant architectural events over time.
-
E.
historicSeeOf
Indicates that a place serves or has served as the principal episcopal seat or central ecclesiastical jurisdiction of a bishop or similar religious authority.
- 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_69ff397e19a88190a945b826159f5290 |
completed | May 9, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69ff392400d0819088d30d08d4a774bd |
completed | May 9, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69ff397d6a2081908fa8f62e8902421b |
completed | May 9, 2026, 1:41 p.m. |
Created at: April 29, 2026, 9:16 p.m.