Triple

T35274132
Position Surface form Disambiguated ID Type / Status
Subject Jorja Interlude E1018749 entity
Predicate includedInProjectType P12865 FINISHED
Object playlist project 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: playlist project | Statement: [Jorja Interlude, includedInProjectType, playlist project]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includedInProjectType
Context triple: [Jorja Interlude, includedInProjectType, playlist project]
  • A. hasProjectType chosen
    Indicates that an entity is associated with, or classified under, a specific type or category of project.
  • B. eligibleProjectType
    Indicates that a project belongs to a category or type that qualifies it for a specific program, process, or benefit.
  • C. includedProject
    Indicates that one project is contained within, or forms a part of, another project.
  • D. supportsProjectType
    Indicates that one entity is capable of handling, accommodating, or being compatible with a specified type of project.
  • E. associatedProjectType
    Indicates that one entity is linked to or categorized under a particular type of project.
  • 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_69f76de5c4788190896ad598ae7d6bc6 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_6a037c8c34f88190ace26f555827f23e completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a0324d08190ac5b610cc0f6a38c completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:02 p.m.