Triple
T6868870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lochmaddy |
E158485
|
entity |
| Predicate | hasBayOrInlet |
P47386
|
FINISHED |
| Object | Lochmaddy sea loch |
—
|
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: Lochmaddy sea loch | Statement: [Lochmaddy, hasBayOrInlet, Lochmaddy sea loch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBayOrInlet Context triple: [Lochmaddy, hasBayOrInlet, Lochmaddy sea loch]
-
A.
hasNotableBay
Indicates that a place possesses a bay that is recognized for its significance, prominence, or special interest.
-
B.
hasInlet
Indicates that one entity serves as an inlet or entry point through which another entity receives a flow of material, energy, or fluid.
-
C.
hasIslandAtMouth
Indicates that a geographic feature, typically a river, has an island located at or near its mouth where it meets a larger body of water.
-
D.
hasHarbourEntrance
Indicates that an entity serves as the entrance or access point to a harbour for another entity.
-
E.
bayOf
chosen
Indicates that one location is a bay that forms an inlet or coastal indentation associated with another geographic entity, such as a sea, ocean, or coastline.
- 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_69c68831e3648190a643c328122e4d43 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6da3ce95081909a424ac04bc7fa07 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b168908190b2f7c724b1bc7fc9 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:22 p.m.