Triple
T5391644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whernside (historical West Riding area) |
E120343
|
entity |
| Predicate | prominenceFeet |
P10298
|
FINISHED |
| Object | 1512 |
—
|
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: 1512 | Statement: [Whernside (historical West Riding area), prominenceFeet, 1512]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominenceFeet Context triple: [Whernside (historical West Riding area), prominenceFeet, 1512]
-
A.
prominence
Indicates that an entity stands out in importance, visibility, or influence relative to others within a given context.
-
B.
prominenceStatus
Indicates the degree to which something is notable, distinguished, or stands out in importance or visibility relative to others.
-
C.
topographicProminence
chosen
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.
-
D.
hasProminence
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
-
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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd8719ff04819089e3a90f90b5e3fc |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.