Triple

T11368726
Position Surface form Disambiguated ID Type / Status
Subject Elbert Guillory E269283 entity
Predicate givenName P17 FINISHED
Object Elbert E47269 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: Elbert | Statement: [Elbert Guillory, givenName, Elbert]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Elbert
Context triple: [Elbert Guillory, givenName, Elbert]
  • A. Elbert chosen
    Elbert is a masculine given name of English origin, historically borne by figures such as American lawyer and steel industry executive Elbert H. Gary.
  • B. Mount Elbert
    Mount Elbert is the highest peak in the Rocky Mountains and the tallest mountain in Colorado, located in the Sawatch Range.
  • C. Elbert, Colorado
    Elbert, Colorado is a small unincorporated community and census-designated place in Elbert County, known for its rural character on the Colorado plains.
  • D. Longs Peak
    Longs Peak is a prominent fourteener in Colorado’s Front Range, renowned for its dramatic profile and challenging Keyhole Route climb.
  • E. Mount Evans
    Mount Evans is a prominent fourteener in Colorado’s Front Range of the Rocky Mountains, known for its high-altitude scenic road and expansive alpine views.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d6aacca1048190b39dbbc2174616fa completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7ea89e1148190b0ca29db9d7e2cbd completed April 9, 2026, 6:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5567b67f88190b0412e30b346d36d completed April 19, 2026, 10:26 p.m.
Created at: April 8, 2026, 9:33 p.m.