Triple
T34609738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usk catchment |
E888691
|
entity |
| Predicate | facesPressureFrom |
P60948
|
FINISHED |
| Object | agricultural diffuse pollution |
—
|
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: agricultural diffuse pollution | Statement: [Usk catchment, facesPressureFrom, agricultural diffuse pollution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facesPressureFrom Context triple: [Usk catchment, facesPressureFrom, agricultural diffuse pollution]
-
A.
surfacePressure
Indicates the pressure exerted by a fluid (such as air or water) on the surface of an object or body.
-
B.
pressureFrom
Indicates a relationship where one entity exerts influence, coercion, or force on another to affect its decisions, actions, or state.
-
C.
hasHumanPressure
chosen
Indicates that one entity exerts or experiences human-induced influence, stress, or impact in relation to another entity or environment.
-
D.
facedPressureFrom
Indicates that one entity experienced coercion, influence, or stress exerted by another entity to act or decide in a certain way.
-
E.
pressureType
Indicates the specific category or kind of pressure associated with an entity or interaction.
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:03 a.m.