Triple
T28641984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eilean Molach |
E724950
|
entity |
| Predicate | waterTypeOfSurroundingLoch |
P180228
|
FINISHED |
| Object | freshwater |
—
|
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: freshwater | Statement: [Eilean Molach, waterTypeOfSurroundingLoch, freshwater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterTypeOfSurroundingLoch Context triple: [Eilean Molach, waterTypeOfSurroundingLoch, freshwater]
-
A.
hasLoch
Indicates that one entity possesses, contains, or features a loch (lake or sea inlet) as part of its characteristics or composition.
-
B.
lakeTypeNearby
Indicates that one entity is located near another entity that is classified as a particular type of lake.
-
C.
mouthLake
Indicates the location where a river or stream flows into and forms part of a lake.
-
D.
waterbodyType
Indicates the classification of a water body according to its type (e.g., river, lake, ocean, etc.).
-
E.
waterbodyUsedFor
Indicates that a particular water body is utilized for a specific purpose, activity, or function.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
| PDg | Predicate description generation | batch_69f739a58b3c81908abc2b8738a65678 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 28, 2026, 4:45 a.m.