Triple
T27480720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wyre catchment |
E693590
|
entity |
| Predicate | flowsToBodyOfWater |
P164325
|
FINISHED |
| Object | Irish Sea |
—
|
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: Irish Sea | Statement: [Wyre catchment, flowsToBodyOfWater, Irish Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsToBodyOfWater Context triple: [Wyre catchment, flowsToBodyOfWater, Irish Sea]
-
A.
flowsIntoBodyOfWaterAt
Indicates that one body of water moves or drains into another body of water at a specific location or point.
-
B.
flowsIntoBodyOfWaterType
Indicates that one body of water moves or drains into another body of water of a specified type (e.g., river, lake, ocean).
-
C.
flowsIntoBodyOfWaterNear
Indicates that one body of water flows into another body of water at or near a specific location.
-
D.
hasBodyOfWaterDrainedBy
Indicates that a body of water is emptied or its water flow is carried away by a specified draining feature, such as a river, channel, or drainage system.
-
E.
flowsIntoBodyOfWaterNearCity
Indicates that a body of water flows into another body of water located in the vicinity of a specified city.
- F. None of above. chosen
Provenance (4 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 12:59 p.m.