Triple
T9227288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samuel Hitt Elbert |
E221717
|
entity |
| Predicate | familyName |
P18
|
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: [Samuel Hitt Elbert, familyName, Elbert]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Elbert Context triple: [Samuel Hitt Elbert, familyName, 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.
Longs Peak
Longs Peak is a prominent fourteener in Colorado’s Front Range, renowned for its dramatic profile and challenging Keyhole Route climb.
-
D.
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.
-
E.
Mount Sneffels
Mount Sneffels is a prominent and rugged fourteener in southwestern Colorado, renowned for its dramatic profile and popular alpine climbing routes.
- 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_69ca83ec8db08190a9110df8232885d2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda9ecef48190b8aa0e316d07cec7 |
completed | April 1, 2026, 8:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0665cd43481908287b6d4858d63a1 |
completed | April 4, 2026, 1:16 a.m. |
Created at: March 30, 2026, 7:28 p.m.