Triple
T33089638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Tiger 3 Trail |
E846741
|
entity |
| Predicate | hasSummitDestination |
P33907
|
FINISHED |
| Object | West Tiger 3 |
—
|
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: West Tiger 3 | Statement: [West Tiger 3 Trail, hasSummitDestination, West Tiger 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitDestination Context triple: [West Tiger 3 Trail, hasSummitDestination, West Tiger 3]
-
A.
hasSummit
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
-
B.
hasSummitIn
Indicates that an entity (such as a mountain or organization) has its summit or peak located within a specified place or region.
-
C.
hasSummitMarker
Indicates that a location or peak is marked by an official summit marker or sign denoting its highest point.
-
D.
hasSummitTrail
chosen
Indicates that there exists a trail or route leading to the summit or highest point of a geographic feature.
-
E.
hasSummitCoordinates
Indicates that an entity has specific geographic coordinates identifying the location of its summit.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: May 1, 2026, 1:26 a.m.