Triple
T38094624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuan Loch Garman |
E951209
|
entity |
| Predicate | formedByEstuaryOf |
P117224
|
FINISHED |
| Object | River Slaney |
—
|
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 Slaney | Statement: [Cuan Loch Garman, formedByEstuaryOf, River Slaney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedByEstuaryOf Context triple: [Cuan Loch Garman, formedByEstuaryOf, River Slaney]
-
A.
locatedInEstuarySystem
chosen
Indicates that something is situated within or forms part of an estuary system, where riverine and marine environments interact.
-
B.
hasEstuaryAt
Indicates that a river or watercourse flows into and meets a larger body of water (such as a sea, ocean, or lake) at a specific location.
-
C.
estuaryName
Indicates the naming relationship that assigns a specific name to an estuary.
-
D.
hasEstuaryWith
Indicates that a river or watercourse flows into and forms an estuary with a particular body of water.
-
E.
hasEstuaryNear
Indicates that the estuary of a water body is located in close proximity to a specified place or feature.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a013632a3048190b05716d803f34716 |
completed | May 11, 2026, 1:51 a.m. |
| PD | Predicate disambiguation | batch_6a01309582e48190a05d47d96ffb7a46 |
completed | May 11, 2026, 1:27 a.m. |
Created at: May 3, 2026, 4:21 p.m.