Triple
T38288460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chilnualna Falls trailhead near Wawona |
E1022285
|
entity |
| Predicate | hasViewDestination |
P854
|
FINISHED |
| Object | Chilnualna Falls viewpoints |
—
|
NE NERFINISHED |
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: Chilnualna Falls viewpoints | Statement: [Chilnualna Falls trailhead near Wawona, hasViewDestination, Chilnualna Falls viewpoints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewDestination Context triple: [Chilnualna Falls trailhead near Wawona, hasViewDestination, Chilnualna Falls viewpoints]
-
A.
hasView
chosen
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
-
B.
hasMainDestination
Indicates that an entity is primarily intended to go to, serve, or be directed toward a particular destination.
-
C.
hasDestinationState
Indicates that an entity is associated with, directed toward, or results in a particular destination state or condition.
-
D.
hasParticularView
Indicates that one entity holds, expresses, or is characterized by a specific opinion, perspective, or standpoint regarding something.
-
E.
hasRouteDestination
Indicates that a route leads to or terminates at a specified destination.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: May 3, 2026, 4:30 p.m.