Triple
T8185201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Trident |
E191163
|
entity |
| Predicate | topographicProminenceType |
P74677
|
FINISHED |
| Object | local summit 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: local summit prominence | Statement: [Mount Trident, topographicProminenceType, local summit prominence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topographicProminenceType Context triple: [Mount Trident, topographicProminenceType, local summit prominence]
-
A.
topographicProminence
Indicates the height of a peak’s summit relative to the lowest contour line encircling it and no higher summit, expressing how much it stands out from surrounding terrain.
-
B.
prominenceType
chosen
Indicates the specific kind or category of prominence or notability associated with an entity in a given context.
-
C.
hasHighestPointType
Indicates that the highest point of an entity is of a specified type or category.
-
D.
elevationType
Indicates the kind or classification of elevation associated with an entity, such as how its height or altitude is characterized.
-
E.
prominenceRelativeToKibo
Indicates how prominent or noticeable one entity is in comparison to Kibo.
- 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_69ca82c4538081909404325aa5639483 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c507f248190b599b4a629b7518a |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:41 p.m.