Triple
T32998021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Swilly |
E844280
|
entity |
| Predicate | inflowsToBodyOfWater |
P36348
|
FINISHED |
| Object | Lough Swilly |
—
|
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: Lough Swilly | Statement: [River Swilly, inflowsToBodyOfWater, Lough Swilly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inflowsToBodyOfWater Context triple: [River Swilly, inflowsToBodyOfWater, Lough Swilly]
-
A.
flowsIntoBodyOfWaterAt
Indicates that one body of water moves or drains into another body of water at a specific location or point.
-
B.
flowsToBodyOfWater
Indicates that a fluid or water source moves or is directed into a specified body of water.
-
C.
flowsIntoBodyOfWaterType
Indicates that one body of water moves or drains into another body of water of a specified type (e.g., river, lake, ocean).
-
D.
flowsIntoBodyOfWaterNear
Indicates that one body of water flows into another body of water at or near a specific location.
-
E.
inflowWatercourse
chosen
Indicates that one watercourse flows into or feeds another water body or watercourse.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d2195f7481908085a8a8eb54342f |
completed | May 3, 2026, 4:42 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:22 a.m.