Triple
T26072039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grisedale valley |
E657575
|
entity |
| Predicate | hasTypicalLandform |
P940
|
FINISHED |
| Object | U-shaped valley |
—
|
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: U-shaped valley | Statement: [Grisedale valley, hasTypicalLandform, U-shaped valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalLandform Context triple: [Grisedale valley, hasTypicalLandform, U-shaped valley]
-
A.
hasLandform
chosen
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
B.
hasLandformOrigin
Indicates that something originates from, or is formed by, a particular landform.
-
C.
hasMountainousTerrain
Indicates that a location or area possesses predominantly mountainous physical terrain or landscape features.
-
D.
landerType
Indicates the specific kind or category of lander involved in the relationship or action.
-
E.
dominantLandformOf
Indicates that one landform is the primary or most characteristic physical feature of a specified geographic area.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 26, 2026, 7:30 p.m.