Triple
T25266974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garnet Canyon |
E633456
|
entity |
| Predicate | trailStartsNear |
P12052
|
FINISHED |
| Object | Jenny Lake area |
—
|
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: Jenny Lake area | Statement: [Garnet Canyon, trailStartsNear, Jenny Lake area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailStartsNear Context triple: [Garnet Canyon, trailStartsNear, Jenny Lake area]
-
A.
startedNear
Indicates that one event or action began close in time or space to another event or action.
-
B.
hasNearbyTrail
chosen
Indicates that one entity is located close to or within a short distance of a trail.
-
C.
tourStartApprox
Indicates that the starting time or date of a tour is known only approximately rather than as an exact value.
-
D.
hasNearbyTrailFeature
Indicates that one entity has another entity as a trail-related feature located in close physical proximity.
-
E.
trailEndpoint
Indicates that one entity marks the terminal point or ending location of a trail defined by another entity.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48398ac488190a781482fc561ed60 |
completed | May 1, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:16 p.m.