Triple

T23053142
Position Surface form Disambiguated ID Type / Status
Subject Amanda Foreman E574075 entity
Predicate hasFanBaseFor P150794 FINISHED
Object her portrayal of Meghan Rotundi 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: her portrayal of Meghan Rotundi | Statement: [Amanda Foreman, hasFanBaseFor, her portrayal of Meghan Rotundi]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFanBaseFor
Context triple: [Amanda Foreman, hasFanBaseFor, her portrayal of Meghan Rotundi]
  • A. hasFanBaseFrom
    Indicates that an entity has a significant group of supporters or followers originating from a specified place, group, or source.
  • B. hasFanBaseDepictedAs
    Indicates that an entity has a fan base that is visually or narratively represented in some form (e.g., in media, artwork, or documentation).
  • C. hasFanBasePrimarilyIn
    Indicates that an entity’s main or largest group of supporters, followers, or fans is located in a specified place or region.
  • D. hasGlobalFanBase
    Indicates that an entity is widely recognized and followed by fans across multiple countries or regions.
  • E. hasFanBaseTension
    Indicates a relationship where there is conflict, rivalry, or strained relations between the fan bases of the related entities.
  • 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_69e245ba7ae48190be606dbc54120e39 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1867dfac48190bf300f85d2907854 completed April 29, 2026, 4:18 a.m.
PD Predicate disambiguation batch_69ef89d5f71881908b9f9d0c8aab278c completed April 27, 2026, 4:07 p.m.
PDg Predicate description generation batch_69ef9b7494f4819088ae59ea3d0ae8ab completed April 27, 2026, 5:23 p.m.
Created at: April 17, 2026, 3:54 p.m.