Triple
T26070063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burrows Trail |
E657516
|
entity |
| Predicate | viewFromRoute |
P9787
|
FINISHED |
| Object | scenic views from Camel's Hump summit |
—
|
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: scenic views from Camel's Hump summit | Statement: [Burrows Trail, viewFromRoute, scenic views from Camel's Hump summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewFromRoute Context triple: [Burrows Trail, viewFromRoute, scenic views from Camel's Hump summit]
-
A.
viewIs
Indicates that one entity is a visual representation or perspective of another entity.
-
B.
viewsAs
Indicates that one entity perceives, interprets, or regards another entity in a particular way or role.
-
C.
viewOver
Indicates that one entity has a visual perspective overlooking or facing another entity, typically providing a vantage point onto it.
-
D.
viewOnValue
Indicates a relationship where one entity holds or expresses a particular perspective, opinion, or stance regarding a specific value or principle.
-
E.
viewpointFrom
chosen
Indicates a relationship where something is observed, depicted, or described from the perspective or location of a particular entity or point.
- 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_69f606ca69b08190977693fd1f8e8ae4 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:28 p.m.