Triple

T21716511
Position Surface form Disambiguated ID Type / Status
Subject New Hampshire 4000-Footers E536043 entity
Predicate hasNotablePeak P10602 FINISHED
Object Mount Hale
Mount Hale is a 4,000-foot-class mountain in New Hampshire’s White Mountains, popular with hikers pursuing the New Hampshire 4000-Footers list.
E1935136 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 Hale | Statement: [New Hampshire 4000-Footers, hasNotablePeak, Mount Hale]
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 Hale
Triple: [New Hampshire 4000-Footers, hasNotablePeak, Mount Hale]
Generated description
Mount Hale is a 4,000-foot-class mountain in New Hampshire’s White Mountains, popular with hikers pursuing the New Hampshire 4000-Footers list.

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_69e0c46c6dd88190a595375fa6ebd701 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69efd96ab4c88190b76f4a6b7c855039 completed April 27, 2026, 9:47 p.m.
NED1 Entity disambiguation (via context triple) batch_6a28c7a394f4819097c064774bc1a5b7 completed June 10, 2026, 2:10 a.m.
NEDg Description generation batch_6a28c9ad2abc819092e3594cd9dce679 completed June 10, 2026, 2:19 a.m.
NED2 Entity disambiguation (via description) batch_6a28ca0facb88190acd8987e118ef8fc completed June 10, 2026, 2:21 a.m.
Created at: April 16, 2026, 6:47 p.m.