Triple

T31439792
Position Surface form Disambiguated ID Type / Status
Subject Pianta Syndicate E802034 entity
Predicate questInvolvement P43670 FINISHED
Object Frankie and Francesca elopement subplot 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: Frankie and Francesca elopement subplot | Statement: [Pianta Syndicate, questInvolvement, Frankie and Francesca elopement subplot]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: questInvolvement
Context triple: [Pianta Syndicate, questInvolvement, Frankie and Francesca elopement subplot]
  • A. questInvolvedIn chosen
    Indicates that an entity participates in, is associated with, or plays a role in a particular quest or mission.
  • B. questType
    Indicates the specific category or nature of a quest that characterizes what kind of mission or objective it represents.
  • C. questedBy
    Indicates that a quest or mission is initiated, assigned, or undertaken by a particular entity.
  • D. stillInvolvedIn
    Indicates that an entity continues to participate in or be associated with a particular activity, role, or relationship at the present time.
  • E. questHubFor
    Indicates a relationship where one entity serves as the central location or main coordination point for quests associated with another 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_69f348c5a6bc819092a557e95438976f completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6abaa1f648190b77073771df3bf3b completed May 3, 2026, 1:58 a.m.
PD Predicate disambiguation batch_69f6aa1e84b88190b025f6ca40f17a8a completed May 3, 2026, 1:51 a.m.
Created at: April 30, 2026, 9:04 p.m.