Triple

T28173518
Position Surface form Disambiguated ID Type / Status
Subject Pinnacle Peak trail E715525 entity
Predicate hasAccessPoint P1985 FINISHED
Object Pinnacle Peak trailhead
Pinnacle Peak trailhead is the main starting point and parking area for hikers accessing the popular Pinnacle Peak hiking trail in Scottsdale, Arizona.
E1806064 NE 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: Pinnacle Peak trailhead | Statement: [Pinnacle Peak trail, hasAccessPoint, Pinnacle Peak trailhead]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Pinnacle Peak trailhead
Triple: [Pinnacle Peak trail, hasAccessPoint, Pinnacle Peak trailhead]
Generated description
Pinnacle Peak trailhead is the main starting point and parking area for hikers accessing the popular Pinnacle Peak hiking trail in Scottsdale, Arizona.

Provenance (5 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_69efd6b340f0819095680e15dcdc1830 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69f6423853ec8190892ecc3e097deeb3 completed May 2, 2026, 6:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15d7bf87e48190ae1d7df3128c8901 completed May 26, 2026, 5:26 p.m.
NEDg Description generation batch_6a15dabd41e481909df6a70b780239b7 completed May 26, 2026, 5:39 p.m.
NED2 Entity disambiguation (via description) batch_6a15db4d7ce88190b7a2331691b812df completed May 26, 2026, 5:41 p.m.
Created at: April 27, 2026, 10:14 p.m.