Triple

T3210797
Position Surface form Disambiguated ID Type / Status
Subject Parícutin E67274 entity
Predicate tephraFallCoverage P46211 FINISHED
Object over 300 km² 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: over 300 km² | Statement: [Parícutin, tephraFallCoverage, over 300 km²]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tephraFallCoverage
Context triple: [Parícutin, tephraFallCoverage, over 300 km²]
  • A. tephraVolume
    Indicates the amount of volcanic tephra produced or present, typically expressed as a measurable volume.
  • B. geologicalHazardZoneFor
    Indicates a relationship where a specified area or zone is identified as being at risk from a particular geological hazard (such as earthquakes, landslides, or volcanic activity).
  • C. landfallLocation
    Indicates the geographic location where a storm or similar weather system first makes landfall.
  • D. isLandslide
    Indicates that an event or condition involves a landslide, where a mass of earth or rock moves down a slope.
  • E. distanceFromHypocenter
    Indicates the measured distance between a specified location and the hypocenter (origin point) of an event such as an earthquake.
  • 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_69ad858ac36c81909962589cd277d6e2 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69adaab886c48190b72e36d0ac855ffe completed March 8, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69ad9e09b83881908801d79c3d9254f9 completed March 8, 2026, 4:04 p.m.
PDg Predicate description generation batch_69ada0f9259c8190afbc5ad0fa55436b completed March 8, 2026, 4:16 p.m.
Created at: March 8, 2026, 3:07 p.m.