Triple

T15193920
Position Surface form Disambiguated ID Type / Status
Subject Heroes and Villains E363095 entity
Predicate hasComplexStructure P28756 FINISHED
Object true 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: true | Statement: [Heroes and Villains, hasComplexStructure, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasComplexStructure
Context triple: [Heroes and Villains, hasComplexStructure, true]
  • A. hasComplex
    Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with another entity.
  • B. hasComplexOwnershipStructure
    Indicates that an entity’s ownership is arranged through multiple layers, parties, or instruments such that control or equity interests are not straightforward to determine.
  • C. hasComplexity chosen
    Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
  • D. hasComplexification
    Indicates that one entity is a more complex or elaborated version, form, or development of another entity.
  • E. hasHighStructure
    Indicates that an entity possesses a high degree of organization, complexity, or well-defined internal structure in relation to another entity or standard.
  • 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_69d85a09a39c81908759f23268e2d408 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0067eb710819085211fd05d5fa5f0 completed April 15, 2026, 9:43 p.m.
PD Predicate disambiguation batch_69deb97bd8bc8190b2ad4888f97cf963 completed April 14, 2026, 10:02 p.m.
Created at: April 10, 2026, 3:10 a.m.