Triple

T28393301
Position Surface form Disambiguated ID Type / Status
Subject Theban Legion tradition E719212 entity
Predicate primaryHagiographer P58465 FINISHED
Object Eucherius of Lyon 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: Eucherius of Lyon | Statement: [Theban Legion tradition, primaryHagiographer, Eucherius of Lyon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryHagiographer
Context triple: [Theban Legion tradition, primaryHagiographer, Eucherius of Lyon]
  • A. primaryWriter
    Indicates that one entity serves as the main or lead author responsible for creating or composing another entity.
  • B. historianAuthor
    Indicates that one entity is the historian who authored or wrote the work represented by the other entity.
  • C. hasHistoricalWritingInfluenceFrom
    Indicates that one entity’s historical writing style, content, or traditions are influenced by those of another entity.
  • D. authorTraditionallyAscribedTo chosen
    Indicates that authorship of a work is customarily or historically attributed to an entity, even if definitive proof of authorship may be uncertain or disputed.
  • E. authorFlourished
    Indicates that an author was actively producing work or was prominent during a specified time period.
  • 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_69eff6efd1b08190ae3cefd4f11388a2 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_6a00315632a8819092290f455babd7ee completed May 10, 2026, 7:18 a.m.
PD Predicate disambiguation batch_6a002f54a0dc81909b0e54c5e110e67c completed May 10, 2026, 7:10 a.m.
Created at: April 28, 2026, 1:15 a.m.