Triple

T18708359
Position Surface form Disambiguated ID Type / Status
Subject Hurricane Andrew E457431 entity
Predicate promptedChange P6009 FINISHED
Object U.S. building codes in South Florida 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: U.S. building codes in South Florida | Statement: [Hurricane Andrew, promptedChange, U.S. building codes in South Florida]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: promptedChange
Context triple: [Hurricane Andrew, promptedChange, U.S. building codes in South Florida]
  • A. reasonForChange chosen
    Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
  • B. changeReason
    Indicates the reason or justification for a modification or change made to an entity or its state.
  • C. changedFrom
    Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
  • D. changedUnder
    Indicates that one entity has undergone alteration, modification, or transformation as a result of the influence, action, or conditions imposed by another entity.
  • E. notableChange
    Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
  • 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_69d8d392aad081909fe31aa03e6e97d1 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e56719383481909d68c9e873ca0800 completed April 19, 2026, 11:36 p.m.
PD Predicate disambiguation batch_69e478de85088190ba5f005f1d39f587 completed April 19, 2026, 6:40 a.m.
Created at: April 10, 2026, 11:50 a.m.