Triple
T22960495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Till (Wiltshire) |
E570881
|
entity |
| Predicate | landUseInValley |
P44109
|
FINISHED |
| Object | predominantly rural |
—
|
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: predominantly rural | Statement: [River Till (Wiltshire), landUseInValley, predominantly rural]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landUseInValley Context triple: [River Till (Wiltshire), landUseInValley, predominantly rural]
-
A.
valleyUsedFor
chosen
Indicates that a valley serves a particular function, purpose, or activity for something or someone.
-
B.
valleyUsedBy
Indicates that a valley is utilized or traversed by a particular entity, such as for passage, habitation, or other activities.
-
C.
valleyLocation
Indicates that one entity is located in, at, or within the geographic bounds of a valley relative to another entity or context.
-
D.
valleyType
Indicates the specific kind or classification of a valley that characterizes the relationship between the entities.
-
E.
landUseContext
Indicates the contextual setting or circumstances under which a particular piece of land is used or designated for a specific purpose.
- 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.