Triple
T11118572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cook’s Meadow Loop Trail |
E262958
|
entity |
| Predicate | offersViewOfFeature |
P3821
|
FINISHED |
| Object | granite cliffs of Yosemite 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: granite cliffs of Yosemite Valley | Statement: [Cook’s Meadow Loop Trail, offersViewOfFeature, granite cliffs of Yosemite Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersViewOfFeature Context triple: [Cook’s Meadow Loop Trail, offersViewOfFeature, granite cliffs of Yosemite Valley]
-
A.
offersViewOf
chosen
Indicates that one entity provides a vantage point from which another entity can be seen or visually appreciated.
-
B.
offersFeature
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
C.
offersEdition
Indicates that one entity provides or makes available a particular version or edition of another entity.
-
D.
offersObject
Indicates that a subject provides or makes available a specific object to another party as an offer.
-
E.
offersModality
Indicates that one entity provides or supports a particular mode, method, or form in which something can be experienced, delivered, or performed.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79af6fe448190b042c2e77b855b05 |
completed | April 9, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:28 p.m.