Triple

T28588377
Position Surface form Disambiguated ID Type / Status
Subject Fieschi assassination attempt E723571 entity
Predicate perpetratorTriedBy P69722 FINISHED
Object French court 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: French court | Statement: [Fieschi assassination attempt, perpetratorTriedBy, French court]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: perpetratorTriedBy
Context triple: [Fieschi assassination attempt, perpetratorTriedBy, French court]
  • A. perpetratorTrial
    Indicates that a legal trial is conducted to judge the actions or guilt of the identified perpetrator.
  • B. perpetratorTrialHeldBy chosen
    Indicates that a legal trial concerning the perpetrator is conducted or overseen by the specified judicial body or authority.
  • C. perpetratedBy
    Indicates that an action, event, or wrongdoing was carried out or caused by a particular agent or entity.
  • D. perpetratorAccordingToConviction
    Indicates that an entity is identified as the perpetrator of an offense according to a formal legal conviction.
  • E. perpetratorType
    Indicates the classification or category of the entity that carried out or is responsible for a harmful, illegal, or otherwise wrongful act.
  • 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_69f01d7f92e481909847f5f3f3174a89 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f65876c52c8190bc889c7a67bd07f3 completed May 2, 2026, 8:03 p.m.
PD Predicate disambiguation batch_69f6575d89788190aca478e4aea05a65 completed May 2, 2026, 7:58 p.m.
Created at: April 28, 2026, 4:19 a.m.