Triple
T2735425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Water of Leith |
E60618
|
entity |
| Predicate | isUrbanRiver |
P39399
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Water of Leith, isUrbanRiver, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanRiver Context triple: [Water of Leith, isUrbanRiver, true]
-
A.
isUrbanRiverOf
chosen
Indicates that a river flows through or is located within an urban area associated with a specified place or city.
-
B.
isUrbanDistrict
Indicates that a given district is classified as an urban administrative or residential area rather than a rural one.
-
C.
isUrbanPark
Indicates that a location is designated and used as a public park within an urban or metropolitan area.
-
D.
isUrbanForest
Indicates that an area of trees and vegetation is located within or closely integrated with an urban or suburban environment.
-
E.
isUrbanizing
Indicates a process in which an area or population becomes more urban in character, typically through increased development, infrastructure, and concentration of people and activities.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb1022488190af84e536946b2e37 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.