Triple
T1660089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pony Track |
E35884
|
entity |
| Predicate | relativePopularity |
P1755
|
FINISHED |
| Object | most commonly used route up Ben Nevis |
—
|
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: most commonly used route up Ben Nevis | Statement: [Pony Track, relativePopularity, most commonly used route up Ben Nevis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePopularity Context triple: [Pony Track, relativePopularity, most commonly used route up Ben Nevis]
-
A.
peakPopularity
Indicates the time or context in which something reaches its highest level of popularity relative to other times or contexts.
-
B.
popularity
chosen
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
C.
rankingImpact
Indicates how an entity’s position or level in a ranking is affected or influenced by another factor or action.
-
D.
isPopularWith
Indicates that one entity is well-liked, favored, or widely accepted by another entity or group.
-
E.
rankComparedTo
Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
- 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_69a88606aa808190aa0b421b4271f220 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa994f92b0819084ee2f6a672334b9 |
completed | March 6, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69a907d2475c8190b7ec7dccd3335eb1 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.