Triple
T24131069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarbidge Mountains |
E597952
|
entity |
| Predicate | approximateTopElevation |
P45909
|
FINISHED |
| Object | over 3000 meters |
—
|
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: over 3000 meters | Statement: [Jarbidge Mountains, approximateTopElevation, over 3000 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateTopElevation Context triple: [Jarbidge Mountains, approximateTopElevation, over 3000 meters]
-
A.
elevationApproxMeters
chosen
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
B.
highestElevationApprox
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
C.
highestPassApproxElevation
Indicates the approximate elevation of the highest pass along a given route or within a specified area.
-
D.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
-
E.
elevationCoverageApproximate
Indicates an approximate or estimated representation of how elevation values are covered or distributed over a given area or dataset.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7788788190a71ad080fc2890a8 |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:25 p.m.