Triple
T13904891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Cocker (Lancashire) |
E334321
|
entity |
| Predicate | natureOfArea |
P86936
|
FINISHED |
| Object | rural countryside |
—
|
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: rural countryside | Statement: [River Cocker (Lancashire), natureOfArea, rural countryside]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natureOfArea Context triple: [River Cocker (Lancashire), natureOfArea, rural countryside]
-
A.
hasNaturalAreaType
Indicates that an entity is associated with or classified by a specific type of natural area (e.g., forest, wetland, grassland).
-
B.
naturalRegionType
Indicates the type or category of natural region to which a given area or place belongs.
-
C.
landAreaCharacteristic
chosen
Indicates a relationship where a land area possesses a particular attribute, quality, or characteristic.
-
D.
nearNaturalRegion
Indicates that one entity is located close to a specified natural region or area in geographic space.
-
E.
naturalRegionOf
Indicates that one entity is the natural geographic region or area in which the other entity is located or to which it belongs.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de25db1e308190aaed6a21e443cc44 |
completed | April 14, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.