Triple
T15258829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jebel Jais |
E364717
|
entity |
| Predicate | ziplineSpeed |
P2096
|
FINISHED |
| Object | up to around 150 km/h (approximate) |
—
|
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: up to around 150 km/h (approximate) | Statement: [Jebel Jais, ziplineSpeed, up to around 150 km/h (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ziplineSpeed Context triple: [Jebel Jais, ziplineSpeed, up to around 150 km/h (approximate)]
-
A.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
B.
spinRate
Indicates the rotational speed at which an object or system is spinning, typically measured as revolutions per unit time.
-
C.
speed
Indicates the rate at which an entity moves or changes position over time.
-
D.
originalLineSpeed
Indicates the speed at which something initially moves or operates before any changes or adjustments are made.
-
E.
maxSpeed
chosen
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084d11148190919eef8e55569bb9 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.