Triple

T318652
Position Surface form Disambiguated ID Type / Status
Subject Indo-Australian Plate E7763 entity
Predicate collidesWith P12942 FINISHED
Object Eurasian Plate in the Himalaya region 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: Eurasian Plate in the Himalaya region | Statement: [Indo-Australian Plate, collidesWith, Eurasian Plate in the Himalaya region]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: collidesWith
Context triple: [Indo-Australian Plate, collidesWith, Eurasian Plate in the Himalaya region]
  • A. overlapsWith
    Indicates that two entities share a common part or region in space, time, or extent, but neither is completely contained within the other.
  • B. collisionType
    Indicates the specific kind or category of collision that occurs between two or more entities.
  • C. collisionSystem
    Indicates a physical interaction where two or more entities impact or collide with each other within a defined system or environment.
  • D. collider
    Indicates that two or more entities participate together in operating or utilizing a particle collider or similar high-energy physics experimental facility.
  • E. coincidesWith
    Indicates that two entities occupy the same position, time, or state such that they exactly overlap or occur together.
  • F. None of above. chosen

Provenance (4 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_69a2e7e7af7881908890039d6be4e9b8 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2eb7df63c8190b7cd1bcfdfd96187 completed Feb. 28, 2026, 1:19 p.m.
PD Predicate disambiguation batch_69a2e94513ec819089f5177f7a521e65 completed Feb. 28, 2026, 1:10 p.m.
PDg Predicate description generation batch_69a2eb7c56bc8190ab787801af2eec8d completed Feb. 28, 2026, 1:19 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.