Triple
T3630559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Machame Route |
E76943
|
entity |
| Predicate | successRateRelative |
P7192
|
FINISHED |
| Object | higher than Marangu Route |
—
|
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: higher than Marangu Route | Statement: [Machame Route, successRateRelative, higher than Marangu Route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successRateRelative Context triple: [Machame Route, successRateRelative, higher than Marangu Route]
-
A.
successRate
chosen
Indicates the proportion or frequency with which attempts at a given action or process result in a successful outcome.
-
B.
successMetric
Indicates the specific criterion or measure used to evaluate whether an action, process, or relationship has achieved its intended success.
-
C.
completionRate
Indicates the proportion of a task, process, or set of items that has been finished relative to its total intended amount.
-
D.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
E.
spinRate
Indicates the rotational speed at which an object or system is spinning, typically measured as revolutions per unit time.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc30136e88190922bb542971b5239 |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.