Triple

T7234833
Position Surface form Disambiguated ID Type / Status
Subject Logan Canyon E155195 entity
Predicate mainRouteBetween P45128 FINISHED
Object Logan, Utah and Bear Lake 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: Logan, Utah and Bear Lake | Statement: [Logan Canyon, mainRouteBetween, Logan, Utah and Bear Lake]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mainRouteBetween
Context triple: [Logan Canyon, mainRouteBetween, Logan, Utah and Bear Lake]
  • A. routeBetween
    Indicates that there exists a path or connection enabling travel or communication between two locations or points.
  • B. significantlyShortensRouteBetween
    Indicates that one entity provides a connection between two others that makes the path or travel distance between them substantially shorter than alternative routes.
  • C. parallelRoute
    Indicates that one route runs alongside and in the same general direction as another route without intersecting it.
  • D. routeVia
    Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
  • E. isMostCommonRouteTo chosen
    Indicates that one route is the most frequently used or typical way to reach a particular destination or outcome compared to all other possible routes.
  • 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_69c688143bfc81908d4176617735e601 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ea552a688190a00f5d0ad982f787 completed March 27, 2026, 8:36 p.m.
PD Predicate disambiguation batch_69c6e7644648819096a5e2de5d0dbe97 completed March 27, 2026, 8:24 p.m.
Created at: March 27, 2026, 2:55 p.m.