Triple

T30057719
Position Surface form Disambiguated ID Type / Status
Subject Tannen E763777 entity
Predicate hasAncestorDescendantTheme P180532 FINISHED
Object multi‑generational antagonists 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: multi‑generational antagonists | Statement: [Tannen, hasAncestorDescendantTheme, multi‑generational antagonists]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAncestorDescendantTheme
Context triple: [Tannen, hasAncestorDescendantTheme, multi‑generational antagonists]
  • A. hasThemeRelationship
    Indicates a relationship where one entity is thematically related to, or centered around, another entity as its main subject or topic.
  • B. hasAncestor
    Indicates that one entity is an ancestor (direct or indirect, such as a parent, grandparent, etc.) of another entity in a genealogical or hierarchical lineage.
  • C. usesThemeFrom
    Indicates that one work incorporates, references, or is based on the thematic material of another work.
  • D. hasAncestralTo
    Indicates that one entity is an ancestor of another, existing in an earlier generation within a lineage or heritage chain.
  • E. hasThemeType
    Indicates that something is associated with or characterized by a particular thematic category or type.
  • 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_69f224716378819087a722e487832b70 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f7431c0eec81909ead443e07d75e18 completed May 3, 2026, 12:44 p.m.
PD Predicate disambiguation batch_69f74143cf708190a12d487884298437 completed May 3, 2026, 12:36 p.m.
PDg Predicate description generation batch_69f7431aac148190bb6aac59817c174a completed May 3, 2026, 12:44 p.m.
Created at: April 29, 2026, 6:57 p.m.