Triple

T19452860
Position Surface form Disambiguated ID Type / Status
Subject Suzanne Warren E486655 entity
Predicate fandomNotability P87366 FINISHED
Object fan-favorite character 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: fan-favorite character | Statement: [Suzanne Warren, fandomNotability, fan-favorite character]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fandomNotability
Context triple: [Suzanne Warren, fandomNotability, fan-favorite character]
  • A. fandomScope
    Indicates the extent or boundaries of a fandom-related relationship, such as how broadly or narrowly a fan’s interest, participation, or recognition applies.
  • B. fandomFocus
    Indicates that one entity is primarily centered on, dedicated to, or concerned with the fan community or fan-related aspects of another entity.
  • C. fandomSignificance chosen
    Indicates the degree to which something holds importance, influence, or prominence within a particular fan community or fandom context.
  • D. fandomContext
    Indicates that the relationship or action occurs specifically within the context of a particular fandom or fan community.
  • E. fandomType
    Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
  • 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_69d8e8d86d608190bd199a98d0297f27 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6339407a08190a3e0213bfbb4df3d completed April 20, 2026, 2:09 p.m.
PD Predicate disambiguation batch_69e4fd7499a4819082bec0be8afba35c completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 1:38 p.m.