Triple

T32202431
Position Surface form Disambiguated ID Type / Status
Subject Mount Humphreys E822577 entity
Predicate topographicMap P10300 FINISHED
Object USGS Mount Tom
USGS Mount Tom is a United States Geological Survey topographic map that covers the Mount Tom area, detailing its terrain, elevations, and geographic features.
E2001067 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: USGS Mount Tom | Statement: [Mount Humphreys, topographicMap, USGS Mount Tom]
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: USGS Mount Tom
Triple: [Mount Humphreys, topographicMap, USGS Mount Tom]
Generated description
USGS Mount Tom is a United States Geological Survey topographic map that covers the Mount Tom area, detailing its terrain, elevations, and geographic features.

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_69f349093174819086e633c190a51aa8 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6bb3c8d7081909b960e469e4d8504 completed May 3, 2026, 3:04 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3056f1b8e481908a0d0248c734baf4 completed June 15, 2026, 7:48 p.m.
NEDg Description generation batch_6a30577fbaa88190ba55c619ab7c180b completed June 15, 2026, 7:50 p.m.
NED2 Entity disambiguation (via description) batch_6a3057fbec6081908738d3aa89e2ef68 completed June 15, 2026, 7:52 p.m.
Created at: May 1, 2026, 12:36 a.m.