Triple
T28185016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homestretch |
E716152
|
entity |
| Predicate | scrambleType |
P145918
|
FINISHED |
| Object | steep rock scramble |
—
|
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: steep rock scramble | Statement: [Homestretch, scrambleType, steep rock scramble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scrambleType Context triple: [Homestretch, scrambleType, steep rock scramble]
-
A.
usesScrambling
Indicates that one entity applies a scrambling process or technique to another entity or to information associated with it.
-
B.
requiresScramble
Indicates that one entity must be mixed, randomized, or rearranged (scrambled) as a necessary condition for another entity, action, or process to occur or be valid.
-
C.
spinType
Indicates the specific kind or category of spin associated with an entity, such as its spin state, mode, or configuration.
-
D.
hasScramblingGrade
chosen
Indicates that an entity is associated with a specific scrambling difficulty grade or level.
-
E.
twistType
Indicates the specific manner or category of twisting applied in a relationship or action between entities.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64285d75481908da4a276fd8c4676 |
completed | May 2, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:22 p.m.