Triple
T5617704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loch of Bosquoy |
E147518
|
entity |
| Predicate | hasWaterBodyForm |
P65035
|
FINISHED |
| Object | 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: loch | Statement: [Loch of Bosquoy, hasWaterBodyForm, loch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterBodyForm Context triple: [Loch of Bosquoy, hasWaterBodyForm, loch]
-
A.
hasWaterBodyCharacteristic
Indicates that a water body possesses a specified physical, chemical, or ecological characteristic.
-
B.
hasAreaWaterBody
Indicates that an entity includes, contains, or is associated with a body of water within its area or boundaries.
-
C.
appliesToWaterBody
Indicates that something (such as a rule, condition, property, or effect) is relevant or applicable specifically to a particular water body.
-
D.
hasMouthWaterbody
Indicates that a waterbody has a mouth, i.e., the location or feature where it empties or flows into another waterbody or area.
-
E.
hasWaterFeatures
Indicates that an entity includes or is associated with water-related elements such as fountains, ponds, streams, or similar features.
- 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_69c00905d4588190bd967842bbcf2219 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c021dc04c081909f36e40394e7c955 |
completed | March 22, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f4032408190a4f0d2eb21ebd870 |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:40 p.m.