Triple

T15413077
Position Surface form Disambiguated ID Type / Status
Subject Kalimari Desert E368640 entity
Predicate obstacleBehavior P52690 FINISHED
Object train blocks the main road at crossing 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: train blocks the main road at crossing | Statement: [Kalimari Desert, obstacleBehavior, train blocks the main road at crossing]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: obstacleBehavior
Context triple: [Kalimari Desert, obstacleBehavior, train blocks the main road at crossing]
  • A. obstacles chosen
    Indicates that one entity presents barriers, hindrances, or impediments that block or restrict another entity’s progress, action, or interaction.
  • B. obstacleHeightCharacteristic
    Indicates the characteristic or measured value of an obstacle’s height in relation to a reference level or path.
  • C. seeksToAvoid
    Indicates an entity’s intention or effort to stay away from, prevent, or not experience another entity or situation.
  • D. hasObstacleType
    Indicates that an entity is associated with or characterized by a specific type or category of obstacle.
  • E. behaviorNear
    Indicates that one entity exhibits a behavior or action in close spatial proximity to 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_69d85a16c68c819099c1b547fbc87b32 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03ea7561481909b04e613e2352f82 completed April 16, 2026, 1:43 a.m.
PD Predicate disambiguation batch_69ded27f45548190a6d2b1b85cb47444 completed April 14, 2026, 11:49 p.m.
Created at: April 10, 2026, 3:20 a.m.