Triple

T36129515
Position Surface form Disambiguated ID Type / Status
Subject Lego DC Comics Super Heroes: Justice League vs. Bizarro League E1044975 entity
Predicate featuresCounterpartTeam P131747 FINISHED
Object Bizarro League E2171061 NE 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: Bizarro League | Statement: [Lego DC Comics Super Heroes: Justice League vs. Bizarro League, featuresCounterpartTeam, Bizarro League]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: featuresCounterpartTeam
Context triple: [Lego DC Comics Super Heroes: Justice League vs. Bizarro League, featuresCounterpartTeam, Bizarro League]
  • A. featuresTeamUp
    Indicates that two or more entities collaborate or join forces to act together as a team.
  • B. featuresTeams chosen
    Indicates that something prominently presents or includes specific teams as a central element or focus.
  • C. featuredTierTwoTeam
    Indicates that a team is highlighted or given special prominence as a second-tier featured team in a given context.
  • D. featuredTeam
    Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
  • E. coreTeams
    Indicates that the entities are part of the same primary or central team within an organization or project.
  • F. None of above.

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_69f76e356c908190abc6ca1e6a05b011 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_6a037c8d06cc8190ab6a5e18d9d2571e completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a390d3ffd38819086ca884737c884fb completed June 22, 2026, 10:24 a.m.
PD Predicate disambiguation batch_6a037a0895b48190acdd88dc10db7be7 completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:08 p.m.