Triple

T4660373
Position Surface form Disambiguated ID Type / Status
Subject Pudding Lane E102513 entity
Predicate fireAftermath P48782 FINISHED
Object area rebuilt after the Great Fire of London 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: area rebuilt after the Great Fire of London | Statement: [Pudding Lane, fireAftermath, area rebuilt after the Great Fire of London]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fireAftermath
Context triple: [Pudding Lane, fireAftermath, area rebuilt after the Great Fire of London]
  • A. fires
    Indicates that an agent initiates the discharge or ignition of something, such as a weapon, engine, or explosive device, causing it to operate or go off.
  • B. aftermathOf chosen
    Indicates that one event, state, or condition occurs as a consequence or result following another event.
  • C. fireEffect
    Indicates that one entity produces, causes, or is associated with a fire-related impact or consequence on another entity.
  • D. underFire
    Indicates that an entity is being attacked, heavily criticized, or subjected to intense pressure by another entity or group.
  • E. handledAftermathOf
    Indicates that one entity took responsibility for dealing with the consequences or fallout that occurred after another entity’s actions or events.
  • 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_69bd43d823288190952279faa0d1d066 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd632a17cc8190bcdab0a13b89f5c0 completed March 20, 2026, 3:09 p.m.
PD Predicate disambiguation batch_69bd62126b0c81909ba3f21b21e30d54 completed March 20, 2026, 3:04 p.m.
Created at: March 20, 2026, 1:15 p.m.