Triple

T25096375
Position Surface form Disambiguated ID Type / Status
Subject 2016 Kumamoto earthquakes E628599 entity
Predicate occurredNearPlateBoundary P4494 FINISHED
Object Philippine Sea Plate 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: Philippine Sea Plate | Statement: [2016 Kumamoto earthquakes, occurredNearPlateBoundary, Philippine Sea Plate]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: occurredNearPlateBoundary
Context triple: [2016 Kumamoto earthquakes, occurredNearPlateBoundary, Philippine Sea Plate]
  • A. locatedOnTectonicBoundary
    Indicates that one entity is situated directly on or along the tectonic plate boundary associated with another entity.
  • B. locatedOnTectonicPlate chosen
    Indicates that one entity (typically a geographic region or feature) lies upon or is situated on the tectonic plate represented by the other entity.
  • C. affectsSubductionZone
    Indicates that one entity has an influence or impact on the behavior, characteristics, or dynamics of a subduction zone.
  • D. plateBoundaryBetween
    Indicates a geological relationship where a boundary exists between two tectonic plates.
  • E. isPartOfTectonicFeature
    Indicates that one geological entity is a component or subdivision of a larger tectonic feature or structure.
  • 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_69e2ff2f58e881908340527bc5d34f07 completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f497bc12b881908fe3386c66252bf6 completed May 1, 2026, 12:08 p.m.
PD Predicate disambiguation batch_69f49366e8d08190adb4b71fe3a14683 completed May 1, 2026, 11:49 a.m.
Created at: April 18, 2026, 6:25 a.m.