Triple
T12082824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleethorpes |
E287722
|
entity |
| Predicate | hasEstuaryMudflats |
P70899
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [Cleethorpes, hasEstuaryMudflats, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEstuaryMudflats Context triple: [Cleethorpes, hasEstuaryMudflats, yes]
-
A.
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.
-
B.
hasEstuaryType
Indicates the specific type or classification of an estuary associated with a given water body or location.
-
C.
hasEstuaryNear
Indicates that the estuary of a water body is located in close proximity to a specified place or feature.
-
D.
hasWetlandsAtMouth
chosen
Indicates that a watercourse or water body has wetlands located at or surrounding its mouth where it meets another body of water.
-
E.
estuaryDesignation
Indicates that a body of water or coastal area has been formally identified or classified as an estuary.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.