Triple
T4494943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Mease |
E100670
|
entity |
| Predicate | hasLandUseInCatchment |
P25275
|
FINISHED |
| Object | agricultural land |
—
|
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 land | Statement: [River Mease, hasLandUseInCatchment, agricultural land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandUseInCatchment Context triple: [River Mease, hasLandUseInCatchment, agricultural land]
-
A.
hasLandUseCharacter
Indicates that one entity possesses or is associated with a particular type or pattern of land use.
-
B.
hasWatershedUse
chosen
Indicates that a particular type of use, activity, or function is associated with or applied to a watershed.
-
C.
landUseIncludes
Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
-
D.
hasFloodplainUse
Indicates that a floodplain area is being used or designated for a particular purpose or activity.
-
E.
hasHydrologicalFunction
Indicates that something performs a role or action related to the movement, storage, or regulation of water within a hydrological system.
- 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_69bd43cdf15081909a4fa2585ff63b3e |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5572c60881909101b4e65dd5de06 |
completed | March 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1 p.m.