Triple

T6984791
Position Surface form Disambiguated ID Type / Status
Subject New York State Comprehensive Emergency Management Plan E161933 entity
Predicate appliesToPhase P74298 FINISHED
Object pre-incident 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: pre-incident | Statement: [New York State Comprehensive Emergency Management Plan, appliesToPhase, pre-incident]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appliesToPhase
Context triple: [New York State Comprehensive Emergency Management Plan, appliesToPhase, pre-incident]
  • A. appliesToFeature
    Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
  • B. appliesTo
    Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
  • C. appliesDuringCareerPhase
    Indicates that something is relevant or in effect only during a specified phase of an entity’s career.
  • D. appliesAt
    Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
  • E. appliesToConfiguration
    Indicates that something (such as a rule, setting, or operation) is relevant to, affects, or is intended for a particular configuration.
  • 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_69c68855dc0481909b4c7e9e9ed273db completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dbbd926c8190a8b60527bd553fa3 completed March 27, 2026, 7:34 p.m.
PD Predicate disambiguation batch_69c6d7c4a18881908d267137daed828b completed March 27, 2026, 7:17 p.m.
PDg Predicate description generation batch_69c6dbbc00fc8190a18221524b774021 completed March 27, 2026, 7:34 p.m.
Created at: March 27, 2026, 2:31 p.m.