Triple
T27274728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camowen River |
E688153
|
entity |
| Predicate | joinsWatercourseNear |
P157273
|
FINISHED |
| Object | Omagh |
—
|
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: Omagh | Statement: [Camowen River, joinsWatercourseNear, Omagh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinsWatercourseNear Context triple: [Camowen River, joinsWatercourseNear, Omagh]
-
A.
joinsRiverNear
chosen
Indicates that one river or watercourse flows into and merges with another river at or close to a specified location.
-
B.
nearbyWatercourse
Indicates that one entity is located close to or alongside a natural or artificial watercourse, such as a river, stream, or canal.
-
C.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
D.
meetsWaterway
Indicates that one geographic feature or entity comes into contact with or joins a waterway such as a river, canal, or stream.
-
E.
watercourseFor
Indicates that one entity serves as the watercourse (such as a river or channel) associated with, carrying, or draining another entity.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6272737c08190b3d33f2c92fdf2ff |
completed | May 2, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:01 a.m.