Triple

T29645417
Position Surface form Disambiguated ID Type / Status
Subject Bottom-Up Narrows E755984 entity
Predicate maximumTypicalDistance P150843 FINISHED
Object up to Big Springs for day hikers 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 Big Springs for day hikers | Statement: [Bottom-Up Narrows, maximumTypicalDistance, up to Big Springs for day hikers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maximumTypicalDistance
Context triple: [Bottom-Up Narrows, maximumTypicalDistance, up to Big Springs for day hikers]
  • A. typicalRangeMaximum_km chosen
    Indicates the maximum distance, in kilometers, that is typically observed or expected for the range of something.
  • B. typicalLinkDistance
    Indicates the usual or characteristic distance that typically separates two linked or related entities.
  • C. typicalRangeMinimum_km
    Indicates the minimum distance, in kilometers, that is typically observed or expected within a given range for the relationship or measurement in question.
  • D. maximumReach
    Indicates the greatest extent, distance, or limit that something can reach or influence within a given context.
  • E. typicalLength
    Indicates the usual or characteristic length associated with an entity or phenomenon.
  • 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_69f0ef89d2c88190a6d0d5116ccd7cc9 completed April 28, 2026, 5:34 p.m.
NER Named-entity recognition batch_69f73223675481908c1bc3208c0f5284 completed May 3, 2026, 11:31 a.m.
PD Predicate disambiguation batch_69f7317690108190b3aae2cd2e1d069e completed May 3, 2026, 11:28 a.m.
Created at: April 28, 2026, 6:49 p.m.