Triple

T23976327
Position Surface form Disambiguated ID Type / Status
Subject Cathedral Ledge E604376 entity
Predicate accessibleBy P1017 FINISHED
Object Cathedral Ledge Road
Cathedral Ledge Road is a scenic access road in New Hampshire that winds up to the popular rock-climbing and sightseeing destination of Cathedral Ledge.
E2286759 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: Cathedral Ledge Road | Statement: [Cathedral Ledge, accessibleBy, Cathedral Ledge Road]
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: Cathedral Ledge Road
Triple: [Cathedral Ledge, accessibleBy, Cathedral Ledge Road]
Generated description
Cathedral Ledge Road is a scenic access road in New Hampshire that winds up to the popular rock-climbing and sightseeing destination of Cathedral Ledge.

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_69e29543f40c819087700b7a272afb60 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f1d2ba11708190b8587bd006249ff5 completed April 29, 2026, 9:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a46f653c3bc81909e65e65a168b8609 completed July 2, 2026, 11:37 p.m.
NEDg Description generation batch_6a46f73513e48190b1f678271587bf1d completed July 2, 2026, 11:41 p.m.
NED2 Entity disambiguation (via description) batch_6a47207736b48190a48dffe7c4971574 completed July 3, 2026, 2:37 a.m.
Created at: April 17, 2026, 9:26 p.m.