Triple

T23286850
Position Surface form Disambiguated ID Type / Status
Subject Lucy Caroline Lyttelton E589010 entity
Predicate spouseNotableEvent P85988 FINISHED
Object assassinated in the Phoenix Park murders of 1882 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: assassinated in the Phoenix Park murders of 1882 | Statement: [Lucy Caroline Lyttelton, spouseNotableEvent, assassinated in the Phoenix Park murders of 1882]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: spouseNotableEvent
Context triple: [Lucy Caroline Lyttelton, spouseNotableEvent, assassinated in the Phoenix Park murders of 1882]
  • A. hasSpouseNotableEvent chosen
    Indicates that a person’s spouse is associated with a notable event related to that person.
  • B. spouseOfNotableEvent
    Indicates a marital relationship where one spouse is a notable event or is contextually defined through association with a notable event.
  • C. spouseNotableFor
    Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
  • D. spouseAtEvent
    Indicates that two individuals are spouses who are present together at a specific event.
  • E. spouseNotableAward
    Indicates that a person’s spouse has received a notable award or honor.
  • 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_69e25d16e2c08190a291de254703129e completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f19647178c8190bbca5da38472ce05 completed April 29, 2026, 5:25 a.m.
PD Predicate disambiguation batch_69effcf325f88190b320268c3c551abb completed April 28, 2026, 12:18 a.m.
Created at: April 17, 2026, 5 p.m.