Triple
T7860501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drumnadrochit |
E182483
|
entity |
| Predicate | liesOnWaterway |
P58979
|
FINISHED |
| Object | River Enrick |
—
|
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: River Enrick | Statement: [Drumnadrochit, liesOnWaterway, River Enrick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liesOnWaterway Context triple: [Drumnadrochit, liesOnWaterway, River Enrick]
-
A.
isInWaterwaySystem
Indicates that an entity is part of, contained within, or traverses a particular waterway network or system.
-
B.
locatedOnWaterbody
Indicates that an entity is situated on or directly adjacent to a specified body of water.
-
C.
isOnWatercourse
chosen
Indicates that one entity is situated directly on, above, or along the path of a watercourse such as a river, stream, or canal.
-
D.
isWaterfrontThoroughfare
Indicates that a thoroughfare (such as a road, street, or path) is located directly along or adjacent to a body of water.
-
E.
hasWaterwayRole
Indicates that an entity participates in or is associated with a waterway in a specific functional capacity or role.
- 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_69ca82887fd48190975896bf38c4596b |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb36bb6ca4819098bc00739e07cfc8 |
completed | March 31, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:53 p.m.