Triple

T29423493
Position Surface form Disambiguated ID Type / Status
Subject James of the Fiery Face E746217 entity
Predicate hasNotabilityReasonOfReferent P156150 FINISHED
Object turbulent reign 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: turbulent reign | Statement: [James of the Fiery Face, hasNotabilityReasonOfReferent, turbulent reign]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNotabilityReasonOfReferent
Context triple: [James of the Fiery Face, hasNotabilityReasonOfReferent, turbulent reign]
  • A. hasNotabilityFor chosen
    Indicates that an entity is notable, recognized, or significant specifically in relation to a given subject, context, or domain.
  • B. hasNotableReference
    Indicates that one entity makes a significant or noteworthy mention of, or allusion to, another entity.
  • C. hasNotabilityLevel
    Indicates that an entity possesses a specified degree or rank of prominence, importance, or recognition relative to others.
  • D. hasNotabilityNote
    Indicates that there is an associated note or annotation explaining the significance, prominence, or special relevance of the subject.
  • E. lacksNotabilityAs
    Indicates that one entity is considered insufficiently notable or significant to be associated with or classified as the other entity.
  • 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_69f0a7a06e0081908add494075912eb4 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69ffb82be8148190a1c870d467a28c80 completed May 9, 2026, 10:41 p.m.
PD Predicate disambiguation batch_69ffb7bbd550819094052e9a0d0ae320 completed May 9, 2026, 10:39 p.m.
Created at: April 28, 2026, 3:07 p.m.