Triple

T20269956
Position Surface form Disambiguated ID Type / Status
Subject Fiyero E499066 entity
Predicate maritalStatusInNovel P92865 FINISHED
Object married to Sarima 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: married to Sarima | Statement: [Fiyero, maritalStatusInNovel, married to Sarima]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maritalStatusInNovel
Context triple: [Fiyero, maritalStatusInNovel, married to Sarima]
  • A. fictionalMaritalStatus chosen
    Indicates that an entity has a marital status that exists only within a fictional, narrative, or hypothetical context rather than in real life.
  • B. maritalStatusInDisguise
    Indicates that an entity’s true marital status is being concealed or misrepresented, typically appearing different from what it actually is.
  • C. marital status
    Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
  • D. maritalStatusInMyth
    Indicates the marital status or relationship state of an entity as portrayed within a specific myth or mythological tradition.
  • E. marriageCharacterization
    Indicates how a marriage is described, evaluated, or characterized in terms of its qualities, dynamics, or nature.
  • 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_69da6275fa6c8190952924930adee150 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e675dc8e708190b840d687f134c9e8 completed April 20, 2026, 6:52 p.m.
PD Predicate disambiguation batch_69e55b1e5e1c8190ba8a5544b1db9e1d completed April 19, 2026, 10:45 p.m.
Created at: April 11, 2026, 11:42 p.m.