Triple
T6035294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamison Valley |
E134402
|
entity |
| Predicate | scenicClassification |
P9701
|
FINISHED |
| Object | iconic Blue Mountains landscape |
—
|
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: iconic Blue Mountains landscape | Statement: [Jamison Valley, scenicClassification, iconic Blue Mountains landscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scenicClassification Context triple: [Jamison Valley, scenicClassification, iconic Blue Mountains landscape]
-
A.
isPartOfScenicVista
Indicates that something is included within, or contributes to, a larger scenic vista or panoramic view.
-
B.
landscapeType
chosen
Indicates the kind or category of natural terrain or scenery that characterizes a place or area.
-
C.
hasScenicValue
Indicates that something possesses notable aesthetic or visual appeal, often due to its natural beauty or pleasing surroundings.
-
D.
landscapeStyle
Indicates the design style or aesthetic approach applied to a landscape or outdoor environment.
-
E.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056b33a7c8190ad6282286199b192 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.