Triple

T30674972
Position Surface form Disambiguated ID Type / Status
Subject Secret Invasion: Thor E780885 entity
Predicate crossoverEvent P175249 FINISHED
Object Secret Invasion NE NERFINISHED

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: Secret Invasion | Statement: [Secret Invasion: Thor, crossoverEvent, Secret Invasion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: crossoverEvent
Context triple: [Secret Invasion: Thor, crossoverEvent, Secret Invasion]
  • A. crossoverHit
    Indicates that a creative work has achieved significant popularity or success across multiple distinct audience segments, genres, or markets beyond its original target.
  • B. crossoverWork chosen
    Indicates that a work features a crossover, combining characters, settings, or elements from two or more distinct works or franchises into a single creative piece.
  • C. crossesOverWith
    Indicates that one entity intersects or overlaps with another, typically by passing across or through its path, boundary, or extent.
  • D. crossingOf
    Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
  • E. crossErectedBy
    Indicates that a particular cross was constructed, installed, or set up by a specified agent or 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_69f224a7fc208190a07d6d3879b31640 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f739a638748190808e7a2930dce16e completed May 3, 2026, 12:03 p.m.
PD Predicate disambiguation batch_69f732f2dc6c8190a4e86da98cc5eb05 completed May 3, 2026, 11:35 a.m.
Created at: April 29, 2026, 8:32 p.m.