Triple
T6806591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Clun |
E156321
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Clun |
E418508
|
NE 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: Clun | Statement: [River Clun, flowsThrough, Clun]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Clun Context triple: [River Clun, flowsThrough, Clun]
-
A.
Clun
chosen
Clun is a small historic village in the Shropshire Hills of England, known for its medieval castle ruins and picturesque rural setting.
-
B.
Clun Forest
Clun Forest is a remote, sparsely populated upland area in southwest Shropshire, England, known for its rolling hills, ancient woodlands, and traditional sheep farming.
-
C.
Clunie
Clunie is a small village in Perth and Kinross, Scotland, known for its historic parish church and scenic rural surroundings.
-
D.
Glendevon
Glendevon is a small village in Perth and Kinross, Scotland, situated in a scenic glen known for its river, reservoirs, and surrounding hills.
-
E.
Llandovery
Llandovery is a historic market town in Carmarthenshire, Wales, known for its medieval castle ruins and role as a gateway to the Brecon Beacons.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d30a006081908996e31aa7ced0ac |
completed | March 27, 2026, 6:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c71aa27cec81909f45911ffa44ea6f |
completed | March 28, 2026, 12:02 a.m. |
Created at: March 27, 2026, 2:16 p.m.