Triple
T32433818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ystwyth Valley |
E828801
|
entity |
| Predicate | watercourseMouthNear |
P124067
|
FINISHED |
| Object | Aberystwyth |
—
|
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: Aberystwyth | Statement: [Ystwyth Valley, watercourseMouthNear, Aberystwyth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watercourseMouthNear Context triple: [Ystwyth Valley, watercourseMouthNear, Aberystwyth]
-
A.
riverMouthBasin
Indicates that a river’s mouth lies within or drains into a particular drainage basin.
-
B.
mouthOfWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water or another watercourse.
-
C.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
-
D.
riverMouthAt
chosen
Indicates that the mouth or endpoint of a river is located at a specified place or geographic feature.
-
E.
nearbyWatercourse
Indicates that one entity is located close to or alongside a natural or artificial watercourse, such as a river, stream, or canal.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 1, 2026, 12:55 a.m.