Triple

T35526178
Position Surface form Disambiguated ID Type / Status
Subject IWGP Junior Heavyweight Championship E1026676 entity
Predicate hasScriptedOutcomes P108535 FINISHED
Object yes 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: yes | Statement: [IWGP Junior Heavyweight Championship, hasScriptedOutcomes, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasScriptedOutcomes
Context triple: [IWGP Junior Heavyweight Championship, hasScriptedOutcomes, yes]
  • A. scriptedOutcome
    Indicates that the outcome of an event or interaction is predetermined or controlled according to a script rather than arising spontaneously.
  • B. hasScriptedNature chosen
    Indicates that something is predetermined or follows a written or planned script rather than occurring spontaneously.
  • C. canBeScripted
    Indicates that the action or behavior can be defined, controlled, or automated through a script or scripting mechanism.
  • D. hasScriptStatus
    Indicates that an entity has a particular script-related state or condition, such as whether a script is present, active, or in a given status.
  • E. hasNarrativeOutcome
    Indicates that an event, action, or narrative element leads to or results in a particular story-related consequence or resolution.
  • 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_69f76dfe78b081908e2b14cb88dd8c00 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fd49f6dbac81909744373a357b7982 completed May 8, 2026, 2:27 a.m.
PD Predicate disambiguation batch_69fd48ed68f481908374183c66a6b055 completed May 8, 2026, 2:22 a.m.
Created at: May 3, 2026, 4:04 p.m.