Triple
T25413234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irish Sea drainage basin |
E636759
|
entity |
| Predicate | includesEstuary |
P178746
|
FINISHED |
| Object | Mersey Estuary |
—
|
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: Mersey Estuary | Statement: [Irish Sea drainage basin, includesEstuary, Mersey Estuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesEstuary Context triple: [Irish Sea drainage basin, includesEstuary, Mersey Estuary]
-
A.
isEstuarine
Indicates that something is located in, formed in, or characteristic of an estuary, where river and seawater environments meet.
-
B.
hasEstuaryWith
Indicates that a river or watercourse flows into and forms an estuary with a particular body of water.
-
C.
hasEstuaryAt
Indicates that a river or watercourse flows into and meets a larger body of water (such as a sea, ocean, or lake) at a specific location.
-
D.
hasEstuaryType
Indicates the specific type or classification of an estuary associated with a given water body or location.
-
E.
locatedInEstuarySystem
Indicates that something is situated within or forms part of an estuary system, where riverine and marine environments interact.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 21, 2026, 1:55 p.m.