Triple

T28110722
Position Surface form Disambiguated ID Type / Status
Subject Kundiman E710480 entity
Predicate hasGenreType P173060 FINISHED
Object love song 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: love song | Statement: [Kundiman, hasGenreType, love song]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGenreType
Context triple: [Kundiman, hasGenreType, love song]
  • A. hasGenreRelation
    Indicates that there is an association between an entity and a specific genre, specifying the type or category it belongs to.
  • B. hasGenreAsSetting
    Indicates that a work’s setting is characterized by, or takes place within, a particular genre.
  • C. hasGenreFeature
    Indicates that something possesses a characteristic, element, or trait associated with a particular genre.
  • D. hasGivenGenre chosen
    Indicates that an entity is associated with a specific genre that has been assigned or designated to it.
  • E. hasUseGenre
    Indicates that something (such as a work, product, or item) is associated with or categorized under a particular genre for its use or purpose.
  • 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_69ef9b71fdb081908b4a61cd7ff147c1 completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f71f8ee0688190bd025f27993452d3 completed May 3, 2026, 10:12 a.m.
PD Predicate disambiguation batch_69f71cc405c08190863565609a4c8499 completed May 3, 2026, 10 a.m.
Created at: April 27, 2026, 9:11 p.m.