Triple

T14707924
Position Surface form Disambiguated ID Type / Status
Subject Mercy (Arya) chapter E345474 entity
Predicate hasFandomDesignation P115447 FINISHED
Object Mercy sample chapter 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: Mercy sample chapter | Statement: [Mercy (Arya) chapter, hasFandomDesignation, Mercy sample chapter]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFandomDesignation
Context triple: [Mercy (Arya) chapter, hasFandomDesignation, Mercy sample chapter]
  • A. fandomSignificance
    Indicates the degree to which something holds importance, influence, or prominence within a particular fan community or fandom context.
  • B. fandomType
    Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
  • C. fandomIdentity
    Indicates that an entity identifies as a fan or member of a particular fandom associated with another entity.
  • D. fandomCharacteristic
    Indicates that an entity possesses a particular trait, behavior, or quality specifically in the context of its fandom or fan community.
  • E. hasFandomWithinStory
    Indicates that within the narrative of a story, one entity is a fan or admirer of another entity (such as a character, group, or work) that exists inside that same story world.
  • F. None of above. chosen

Provenance (4 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_69d822e4a8c08190a155df736bb7bc13 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb609965081908f654bcb9eaaa145 completed April 14, 2026, 9:47 p.m.
PD Predicate disambiguation batch_69de657c57ec8190ae0b9bb79a514566 completed April 14, 2026, 4:04 p.m.
PDg Predicate description generation batch_69de716d3aac8190aaa6dc1f099b86e8 completed April 14, 2026, 4:55 p.m.
Created at: April 10, 2026, 1:28 a.m.