Triple

T18845961
Position Surface form Disambiguated ID Type / Status
Subject Gala (place-name associated with Galashiels) E460913 entity
Predicate toponymicRole P122228 FINISHED
Object source of hydronym for Gala Water 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: source of hydronym for Gala Water | Statement: [Gala (place-name associated with Galashiels), toponymicRole, source of hydronym for Gala Water]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: toponymicRole
Context triple: [Gala (place-name associated with Galashiels), toponymicRole, source of hydronym for Gala Water]
  • A. hasTopographicalRole
    Indicates that an entity serves a specific functional or positional role within a topographical or spatial context.
  • B. geographicRole
    Indicates a relationship where one entity serves a specific geographic function, status, or role in relation to another location or area.
  • C. toponymicFunction
    Indicates that one entity functions as a place-related name or designation for another entity, typically identifying or characterizing it by a geographic location.
  • D. typeOfToponym
    Indicates the specific category or kind of place name (toponym) that applies to a given geographic entity.
  • E. hasToponymicAssociation chosen
    Indicates a relationship where one entity is associated with, derived from, or named after a particular place or geographic name (toponym).
  • 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_69d8dcfa11e4819090ab1ef5bdcd2b2e completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5b8ee96988190bf247b986777945c completed April 20, 2026, 5:26 a.m.
PD Predicate disambiguation batch_69e48d1e7dac81909ea1e758c87773c5 completed April 19, 2026, 8:06 a.m.
Created at: April 10, 2026, 11:56 a.m.