Triple

T2590197
Position Surface form Disambiguated ID Type / Status
Subject Zodiac E58101 entity
Predicate difficultyRelativeToOtherElCapRoutes P18073 FINISHED
Object harder than many trade routes 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: harder than many trade routes | Statement: [Zodiac, difficultyRelativeToOtherElCapRoutes, harder than many trade routes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: difficultyRelativeToOtherElCapRoutes
Context triple: [Zodiac, difficultyRelativeToOtherElCapRoutes, harder than many trade routes]
  • A. difficultyRelativeToOtherRoutes chosen
    Indicates how the difficulty level of one route compares relative to other routes.
  • B. difficultyRelativeTo
    Indicates that one entity’s level of difficulty is being compared to and expressed in relation to another entity’s level of difficulty.
  • C. hasTrailDifficulty
    Indicates the level of challenge or effort required to traverse a particular trail or route.
  • D. climbingRoute
    Indicates a relationship where a path or sequence of holds is designated for ascending a surface, typically in rock climbing or similar activities.
  • E. climbingDifficultyStandardRoute
    Indicates the level of difficulty associated with ascending via the standard or most commonly used route.
  • 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_69ab4ac019c8819094add11c46706e32 completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abd3feb45c81909369a49c3990294a completed March 7, 2026, 7:30 a.m.
PD Predicate disambiguation batch_69abd0d19308819089ee942513d567a4 completed March 7, 2026, 7:16 a.m.
Created at: March 6, 2026, 9:49 p.m.