Triple

T17238766
Position Surface form Disambiguated ID Type / Status
Subject General Slocum steamship disaster E418432 entity
Predicate deadliestEventIn P30647 FINISHED
Object history of New York City 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: history of New York City | Statement: [General Slocum steamship disaster, deadliestEventIn, history of New York City]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: deadliestEventIn
Context triple: [General Slocum steamship disaster, deadliestEventIn, history of New York City]
  • A. worstNaturalDisasterIn
    Indicates that a particular natural disaster is the most severe or damaging one that has occurred within a specified location or region.
  • B. deadliestIn chosen
    Indicates that something has the highest lethality or causes the most deaths within a specified context, group, or location.
  • C. notableDeathTollEvent
    Indicates that an event is characterized by causing an unusually large or historically significant number of deaths.
  • D. notableDisasterType
    Indicates the specific kind or category of disaster for which something (such as a place, event, or entity) is notable or best known.
  • E. otherMajorTragedy
    Indicates that the subject experienced or was involved in a significant tragic event other than the primary or most notable tragedy under consideration.
  • 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_69d886d8e96081909870bff6c3d0bf09 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42dfdc8688190aceb223c19a48781 completed April 19, 2026, 1:21 a.m.
PD Predicate disambiguation batch_69e3832553ac819091aa917c84f755b6 completed April 18, 2026, 1:12 p.m.
Created at: April 10, 2026, 5:39 a.m.