Triple

T23807274
Position Surface form Disambiguated ID Type / Status
Subject Lawrence of Rome E589741 entity
Predicate underPersecutionBy P48045 FINISHED
Object Emperor Valerian NE NERFINISHED

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: Emperor Valerian | Statement: [Lawrence of Rome, underPersecutionBy, Emperor Valerian]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: underPersecutionBy
Context triple: [Lawrence of Rome, underPersecutionBy, Emperor Valerian]
  • A. persecutionOf
    Indicates the act of subjecting an entity to persistent, often unjust hostility, harassment, or oppression, typically on the basis of identity, beliefs, or group membership.
  • B. causeOfPersecution
    Indicates that one entity is the reason or basis for another entity being persecuted.
  • C. persecutedIn
    Indicates that an entity is subjected to oppression, harassment, or unfair treatment within a particular place, context, or time period.
  • D. wasPersecutedBy chosen
    Indicates that an entity was subjected to persistent hostility, oppression, or harmful treatment carried out by another entity.
  • E. persecutedAfter
    Indicates that one entity is subjected to persecution by another entity after a specified event or point in time.
  • 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_69e25d19fecc8190a5cf39bbb18d5d7f completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1c752ff6481908cfc20d4f178d526 completed April 29, 2026, 8:54 a.m.
PD Predicate disambiguation batch_69f155fe300481909bd617443228df65 completed April 29, 2026, 12:51 a.m.
Created at: April 17, 2026, 7:56 p.m.