Triple

T25736541
Position Surface form Disambiguated ID Type / Status
Subject Catatumbo lightning E645390 entity
Predicate lightningType P159199 FINISHED
Object predominantly intra-cloud lightning 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: predominantly intra-cloud lightning | Statement: [Catatumbo lightning, lightningType, predominantly intra-cloud lightning]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lightningType
Context triple: [Catatumbo lightning, lightningType, predominantly intra-cloud lightning]
  • A. hasLightningProtection
    Indicates that an entity is equipped with or incorporates a system designed to protect it from lightning strikes or their effects.
  • B. affectedByLightningRod
    Indicates that an entity is influenced, protected, or otherwise impacted as a result of the presence or action of a lightning rod.
  • C. lightType
    Indicates the specific category or kind of light associated with an entity or lighting setup.
  • D. hasLightningLane
    Indicates that an attraction, experience, or location offers access via a Lightning Lane queue or reservation system.
  • E. lighthouseType
    Indicates the specific classification or category of a lighthouse based on its design, function, or operational characteristics.
  • 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_69e77e85254081908d79ee4e8715f283 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f5fcbf71308190a81518c504d5632d completed May 2, 2026, 1:31 p.m.
PD Predicate disambiguation batch_69f4938262ac8190b41f922d0407d272 completed May 1, 2026, 11:50 a.m.
PDg Predicate description generation batch_69f497b8abb88190bb672cf6907c4b8d completed May 1, 2026, 12:08 p.m.
Created at: April 21, 2026, 11:27 p.m.