Triple

T33122664
Position Surface form Disambiguated ID Type / Status
Subject Alive in Joburg E847639 entity
Predicate isExpansionBasisFor P11669 FINISHED
Object feature-length adaptation District 9 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: feature-length adaptation District 9 | Statement: [Alive in Joburg, isExpansionBasisFor, feature-length adaptation District 9]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isExpansionBasisFor
Context triple: [Alive in Joburg, isExpansionBasisFor, feature-length adaptation District 9]
  • A. hasBasisIn
    Indicates that one entity is founded, derived, or justified on the grounds of another entity.
  • B. hasStandardBasis
    Indicates that a given vector space is equipped with or possesses its usual canonical set of basis vectors.
  • C. hasCanonicalBasis
    Indicates that there exists a standard or preferred basis associated with an entity, typically used as the reference basis in its context.
  • D. expandsTo chosen
    Indicates that one entity unfolds, develops, or is elaborated into another, typically more detailed or extensive, representation or form.
  • E. hasExpansionType
    Indicates that an entity is associated with a particular mode or category of expansion (such as how it grows, extends, or scales).
  • 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_69f349588f088190b7c9588860f72033 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d71a52288190bfdbb5c1913a7787 completed May 3, 2026, 5:03 a.m.
PD Predicate disambiguation batch_69f6d27224708190b31a541cebe0ff77 completed May 3, 2026, 4:43 a.m.
Created at: May 1, 2026, 1:27 a.m.