Triple
T3292585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Wensum |
E69134
|
entity |
| Predicate | waterFrameworkStatus |
P47790
|
FINISHED |
| Object | heavily modified water body |
—
|
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: heavily modified water body | Statement: [River Wensum, waterFrameworkStatus, heavily modified water body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterFrameworkStatus Context triple: [River Wensum, waterFrameworkStatus, heavily modified water body]
-
A.
waterwayStatus
Indicates the current navigational or operational condition of a waterway, such as whether it is open, restricted, or closed for use.
-
B.
websiteStatus
Indicates the current operational condition or availability state of a website.
-
C.
waterInfrastructure
Indicates the existence, development, or management of systems and facilities that supply, store, treat, or distribute water between entities.
-
D.
waterVolume
Indicates the amount of water present in or associated with an entity, typically measured as a volume.
-
E.
worksStatus
Indicates the current state or condition of an entity’s work or project, such as whether it is planned, in progress, completed, or otherwise categorized.
- 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_69ad859d45748190b0742408c954b39f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb07379dc8190b7bb409bcf42bdd6 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:10 p.m.