Triple

T27775349
Position Surface form Disambiguated ID Type / Status
Subject Mount Toby caves E699169 entity
Predicate locatedIn P40 FINISHED
Object Mount Toby
Mount Toby is a prominent forested mountain in Sunderland, Massachusetts, known for its extensive hiking trails, diverse ecosystems, and scenic views of the Connecticut River Valley.
E1795426 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: Mount Toby | Statement: [Mount Toby caves, locatedIn, Mount Toby]
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: Mount Toby
Triple: [Mount Toby caves, locatedIn, Mount Toby]
Generated description
Mount Toby is a prominent forested mountain in Sunderland, Massachusetts, known for its extensive hiking trails, diverse ecosystems, and scenic views of the Connecticut River Valley.

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_69ef6a4b5a9081909c9111396c2be3d2 completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f63799f02c81909ca4f4d95728fed7 completed May 2, 2026, 5:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a13113a96c88190986a8920e7db1b71 completed May 24, 2026, 2:54 p.m.
NEDg Description generation batch_6a1311ab8c508190ad4c792ffc0b107b completed May 24, 2026, 2:56 p.m.
NED2 Entity disambiguation (via description) batch_6a1312270be48190a7e7a873281abc47 completed May 24, 2026, 2:58 p.m.
Created at: April 27, 2026, 5:05 p.m.