Triple
T32768176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuttall (hill) |
E837958
|
entity |
| Predicate | hasProminenceCriterion |
P28932
|
FINISHED |
| Object | >= 15 metres |
—
|
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: >= 15 metres | Statement: [Nuttall (hill), hasProminenceCriterion, >= 15 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProminenceCriterion Context triple: [Nuttall (hill), hasProminenceCriterion, >= 15 metres]
-
A.
hasProminence
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
-
B.
hasMinimumProminence
chosen
Indicates that an entity meets or exceeds a specified threshold level of prominence or importance within a given context.
-
C.
elevatedInProminenceBy
Indicates that an entity’s prominence, status, or visibility is increased as a result of the actions or influence of another entity.
-
D.
hasProminenceParent
Indicates that one entity derives its prominence, importance, or highlighted status from another entity that serves as its parent in a prominence hierarchy.
-
E.
isProminentPeak
Indicates that a peak stands out significantly in height, visibility, or importance compared to surrounding peaks.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a011c64ff18819099195701bbecbb20 |
completed | May 11, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_6a011b7f7a508190b2ebb518fb7a2fe9 |
completed | May 10, 2026, 11:57 p.m. |
Created at: May 1, 2026, 1:13 a.m.