Triple
T37322019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pico Simón Bolívar |
E926506
|
entity |
| Predicate | relativeHeightRankInWorld |
P2472
|
FINISHED |
| Object | among top peaks by prominence |
—
|
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: among top peaks by prominence | Statement: [Pico Simón Bolívar, relativeHeightRankInWorld, among top peaks by prominence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeHeightRankInWorld Context triple: [Pico Simón Bolívar, relativeHeightRankInWorld, among top peaks by prominence]
-
A.
hasHeightRanking
Indicates that one entity’s height is ordered or ranked relative to others in a comparative height scale.
-
B.
rankBySizeInWorld
Indicates that entities are ordered according to their relative size within the context of the entire world.
-
C.
regionRankByHeight
Indicates the relative ordering of regions based on their height or elevation.
-
D.
rankByHeightWorld
chosen
Indicates an ordering of entities based on their relative height compared to all others in the world.
-
E.
relativeHeightRankOnJura
Indicates the comparative ranking of an entity’s height specifically within the context of the Jura (e.g., among features or locations in the Jura region).
- 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.