Triple

T34708757
Position Surface form Disambiguated ID Type / Status
Subject Arabia–India–Somalia triple-plate region E1000577 entity
Predicate hasBoundaryProcess P194778 FINISHED
Object rifting 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: rifting | Statement: [Arabia–India–Somalia triple-plate region, hasBoundaryProcess, rifting]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBoundaryProcess
Context triple: [Arabia–India–Somalia triple-plate region, hasBoundaryProcess, rifting]
  • A. hasBoundaryCriterion
    Indicates that something is associated with a specific rule or condition used to define or limit its boundary.
  • B. hasBoundarySystem
    Indicates that one entity possesses or is associated with a specific boundary system that defines its limits or separation from its surroundings.
  • C. hasBoundaryType
    Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
  • D. hasBoundaryEvent
    Indicates that an event occurs at or defines the boundary or limit of another entity or process.
  • E. hasBoundaryFeature
    Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
  • 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_69f76dab937881909c86f1b9ad50445f completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69fd864235b481908738dbb69556bc62 completed May 8, 2026, 6:44 a.m.
PD Predicate disambiguation batch_69fd8373b6bc819091c554f29ee17fec completed May 8, 2026, 6:32 a.m.
PDg Predicate description generation batch_69fd8640e1d4819081c98f15eeb221ab completed May 8, 2026, 6:44 a.m.
Created at: May 3, 2026, 3:59 p.m.