Triple

T20760696
Position Surface form Disambiguated ID Type / Status
Subject Constructicons E510967 entity
Predicate notableStoryRole P42552 FINISHED
Object construction of Decepticon bases 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: construction of Decepticon bases | Statement: [Constructicons, notableStoryRole, construction of Decepticon bases]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableStoryRole
Context triple: [Constructicons, notableStoryRole, construction of Decepticon bases]
  • A. notableWorkRole
    Indicates that a person’s role or position is specifically associated with the creation, performance, or contribution to a notable work.
  • B. roleInStories chosen
    Indicates the specific function, position, or character part an entity plays within one or more stories.
  • C. notableHolderRole
    Indicates that an entity is recognized for holding a particular role, office, or position in a notable or distinguished capacity.
  • D. notableAuthorRole
    Indicates that an entity holds a significant or distinguished role as an author in relation to another entity.
  • E. inNarrativeRole
    Indicates that one entity participates in relation to another by occupying a specific narrative function or role within a story or discourse.
  • 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_69e0b4c909ec8190b05987f1639513f6 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c248701081908ae49fca933e05f6 completed April 21, 2026, 12:18 a.m.
PD Predicate disambiguation batch_69e5c0509608819080cdbf47fcddfe36 completed April 20, 2026, 5:57 a.m.
Created at: April 16, 2026, 12:35 p.m.