Triple

T34640398
Position Surface form Disambiguated ID Type / Status
Subject Silvan Elvish E889538 entity
Predicate fandomStudyArea P179555 FINISHED
Object Tolkienian linguistics 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: Tolkienian linguistics | Statement: [Silvan Elvish, fandomStudyArea, Tolkienian linguistics]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fandomStudyArea
Context triple: [Silvan Elvish, fandomStudyArea, Tolkienian linguistics]
  • 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. fandomType
    Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
  • D. fandomCulture
    Indicates a relationship where one entity is associated with, shaped by, or participates in the shared practices, norms, and creative activities of a particular fan community.
  • E. fandomContext
    Indicates that the relationship or action occurs specifically within the context of a particular fandom or fan community.
  • 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_69f349d724848190b63ad3407e0006d9 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f722c1bc648190a79bfdc722dcaaa4 completed May 3, 2026, 10:26 a.m.
PD Predicate disambiguation batch_69f72157af108190880317a62e634bb0 completed May 3, 2026, 10:20 a.m.
PDg Predicate description generation batch_69f7221bc57c819085c1464a45e61b2f completed May 3, 2026, 10:23 a.m.
Created at: May 1, 2026, 2:04 a.m.