Triple
T26258976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Elk Peak |
E656793
|
entity |
| Predicate | distanceFromMountRushmore |
P45869
|
FINISHED |
| Object | approximately 3.7 miles southwest |
—
|
LITERAL 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: approximately 3.7 miles southwest | Statement: [Black Elk Peak, distanceFromMountRushmore, approximately 3.7 miles southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromMountRushmore Context triple: [Black Elk Peak, distanceFromMountRushmore, approximately 3.7 miles southwest]
-
A.
distanceToMountRushmore
chosen
Indicates the measured or calculated spatial distance between an entity and Mount Rushmore.
-
B.
distanceToWashingtonMonument
Indicates the physical distance between a given entity’s location and the Washington Monument.
-
C.
distanceToDenali
Indicates the measured or estimated spatial distance between a given entity and Denali.
-
D.
distanceToFourCornersMonumentInMiles
Indicates the numerical distance, measured in miles, between an entity’s location and the Four Corners Monument.
-
E.
distanceToWashingtonDC
Indicates the physical distance between a given location and Washington, D.C.
- F. None of above.
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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 26, 2026, 9:09 p.m.