Triple
T22960505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Till (Wiltshire) |
E570881
|
entity |
| Predicate | catchmentLandUse |
P107197
|
FINISHED |
| Object | mixed farming |
—
|
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: mixed farming | Statement: [River Till (Wiltshire), catchmentLandUse, mixed farming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catchmentLandUse Context triple: [River Till (Wiltshire), catchmentLandUse, mixed farming]
-
A.
drainageBasinLandUse
chosen
Indicates how the land within a drainage basin is utilized or managed (e.g., for agriculture, urban development, or natural vegetation).
-
B.
majorLandUse
Indicates the primary way a given area of land is utilized or designated (e.g., residential, commercial, agricultural).
-
C.
hasLandUseCharacter
Indicates that one entity possesses or is associated with a particular type or pattern of land use.
-
D.
landUseContext
Indicates the contextual setting or circumstances under which a particular piece of land is used or designated for a specific purpose.
-
E.
landUseIncludes
Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f3c96081909abd6ec32103d4c3 |
completed | April 29, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:47 p.m.