Triple
T22312417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest Scotland |
E551550
|
entity |
| Predicate | hasMajorLoch |
P59565
|
FINISHED |
| Object | Loch Torridon |
—
|
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: Loch Torridon | Statement: [Northwest Scotland, hasMajorLoch, Loch Torridon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorLoch Context triple: [Northwest Scotland, hasMajorLoch, Loch Torridon]
-
A.
hasLoch
chosen
Indicates that one entity possesses, contains, or features a loch (lake or sea inlet) as part of its characteristics or composition.
-
B.
hasMajorLake
Indicates that a geographic region or area contains at least one significant lake within its boundaries.
-
C.
hasMajorLakeAtSource
Indicates that the source of a river or stream is located in, or directly associated with, a major lake.
-
D.
hasMajorBay
Indicates that an entity possesses or is associated with a primary or significant bay.
-
E.
associatedLoch
Indicates that one entity is linked or connected to a particular loch (lake or sea inlet), typically by location, relevance, or contextual relationship.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1574f97cc81909685aeef15d02af9 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.