Triple

T33760758
Position Surface form Disambiguated ID Type / Status
Subject Atli E865098 entity
Predicate equivalentNameInTradition P86691 FINISHED
Object Attila 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: Attila | Statement: [Atli, equivalentNameInTradition, Attila]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: equivalentNameInTradition
Context triple: [Atli, equivalentNameInTradition, Attila]
  • A. equatedWithInSomeTraditions chosen
    Indicates that, in certain cultural, religious, or scholarly traditions, one entity is regarded as equivalent to or identified with another.
  • B. belongsToNamingTradition
    Indicates that an entity is associated with or classified under a particular naming tradition or convention.
  • C. nameInWesternTradition
    Indicates that an entity’s name is expressed following Western naming conventions, typically with the given name preceding the family name.
  • D. hasTraditionalName
    Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
  • E. mentionedInTraditionOf
    Indicates that something is referenced, recognized, or discussed within the body of beliefs, practices, or narratives of a particular tradition.
  • 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_69f3498d3b748190aa3c4006c1f32f38 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f727bde8f88190ad746ca515134ca1 completed May 3, 2026, 10:47 a.m.
PD Predicate disambiguation batch_69f72739c30c81908642eef3feb3afcf completed May 3, 2026, 10:45 a.m.
Created at: May 1, 2026, 1:45 a.m.