Triple

T25455127
Position Surface form Disambiguated ID Type / Status
Subject Transverse Ranges transportation corridor E637892 entity
Predicate barrierCrossed P85838 FINISHED
Object Transverse Ranges NE NERFINISHED

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: Transverse Ranges | Statement: [Transverse Ranges transportation corridor, barrierCrossed, Transverse Ranges]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: barrierCrossed
Context triple: [Transverse Ranges transportation corridor, barrierCrossed, Transverse Ranges]
  • A. crossingOf
    Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
  • B. crossedBy
    Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
  • C. geographicFeatureCrossed
    Indicates that one geographic feature passes over, through, or across another geographic feature.
  • D. crossesBorderOf
    Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
  • E. isBarrierTo chosen
    Indicates that one entity obstructs, prevents, or significantly hinders another entity from occurring, progressing, or being accessed.
  • 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_69e75db7c5048190b8da9cd7eeedb610 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f725e4d08190b0304e45a417193b completed May 2, 2026, 1:07 p.m.
PD Predicate disambiguation batch_69f4683b34748190818428489a226124 completed May 1, 2026, 8:45 a.m.
Created at: April 21, 2026, 2:04 p.m.