Triple
T25140227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kings Peak Trail |
E629782
|
entity |
| Predicate | servesAsPrimaryRouteTo |
P141321
|
FINISHED |
| Object | Kings Peak |
—
|
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: Kings Peak | Statement: [Kings Peak Trail, servesAsPrimaryRouteTo, Kings Peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAsPrimaryRouteTo Context triple: [Kings Peak Trail, servesAsPrimaryRouteTo, Kings Peak]
-
A.
servesAsRouteTo
chosen
Indicates that one entity functions as a pathway, channel, or means of access leading to another entity.
-
B.
servesAsBaseForRoute
Indicates that one entity functions as the foundational or starting point upon which a route is defined, constructed, or planned.
-
C.
hasPrimaryRoute
Indicates that one entity is designated as the main or principal route associated with another entity.
-
D.
primaryRouteThrough
Indicates that one location or path serves as the main or most significant route passing through another location or area.
-
E.
primaryRouteFrom
Indicates that one entity serves as the main or preferred route originating from 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 18, 2026, 6:29 a.m.