Triple

T1061714
Position Surface form Disambiguated ID Type / Status
Subject Babylon Branch E22920 entity
Predicate hasLevelCrossings P3381 FINISHED
Object no between Jamaica and Babylon 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: no between Jamaica and Babylon | Statement: [Babylon Branch, hasLevelCrossings, no between Jamaica and Babylon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLevelCrossings
Context triple: [Babylon Branch, hasLevelCrossings, no between Jamaica and Babylon]
  • A. hadCrossingPoints
    Indicates that two entities intersected or overlapped at one or more specific points in space or time.
  • B. crossesBetween
    Indicates that one entity passes from one side of a second entity to the other, traversing the space between two reference points or boundaries associated with that second entity.
  • C. hasMajorCrossing
    Indicates that one entity has a significant or primary intersection or crossing with another entity.
  • D. hasAtGradeCrossingNearby chosen
    Indicates that one entity (typically a location or segment) has a nearby at-grade crossing where two transportation paths intersect at the same level.
  • E. crossesSectionOf
    Indicates that one entity passes through or over a specific segment or portion of another entity.
  • 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_69a493dada0481909c43649f9843ea91 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4ba6e35ac8190802341c31bda0e3b completed March 1, 2026, 10:15 p.m.
PD Predicate disambiguation batch_69a4b7340a048190807363f19d17a58f completed March 1, 2026, 10:01 p.m.
Created at: March 1, 2026, 7:42 p.m.