Triple

T2606705
Position Surface form Disambiguated ID Type / Status
Subject Léogâne E58676 entity
Predicate populationImpact2010Earthquake P41205 FINISHED
Object very high casualties and displacement 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: very high casualties and displacement | Statement: [Léogâne, populationImpact2010Earthquake, very high casualties and displacement]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: populationImpact2010Earthquake
Context triple: [Léogâne, populationImpact2010Earthquake, very high casualties and displacement]
  • A. notableEarthquake
    Indicates that an earthquake event is significant or noteworthy due to its magnitude, impact, or historical importance.
  • B. earthquakeMagnitude
    Indicates the measured strength or intensity of an earthquake, typically expressed on a standardized magnitude scale.
  • C. earthquakeType
    Indicates the specific classification or category of an earthquake based on its characteristics or cause.
  • D. relatedEarthquakeZone
    Indicates that one entity is geographically or geologically associated with a particular earthquake-prone zone or seismic region.
  • E. facedMajorEarthquake
    Indicates that an entity has experienced or been subjected to a significant or severe earthquake event.
  • 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_69ab4ac3523881909679750c9f8c2dec completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abd8def9bc8190b2e013abffc7b191 completed March 7, 2026, 7:50 a.m.
PD Predicate disambiguation batch_69abd80ab7248190ba06ba14fe4c5638 completed March 7, 2026, 7:47 a.m.
PDg Predicate description generation batch_69abd8dd05c48190b4f90031642c4091 completed March 7, 2026, 7:50 a.m.
Created at: March 6, 2026, 9:49 p.m.