Triple

T4357222
Position Surface form Disambiguated ID Type / Status
Subject Only God Knows Why E98178 entity
Predicate hasCrossoverAppeal P55746 FINISHED
Object country audience 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: country audience | Statement: [Only God Knows Why, hasCrossoverAppeal, country audience]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCrossoverAppeal
Context triple: [Only God Knows Why, hasCrossoverAppeal, country audience]
  • A. hasAppealsTo
    Indicates that one entity formally challenges or seeks review of a decision, judgment, or outcome through another entity or process.
  • B. hasCross
    Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
  • C. crossesOverWith
    Indicates that one entity intersects or overlaps with another, typically by passing across or through its path, boundary, or extent.
  • D. hasAppellateJurisdictionIn
    Indicates that one legal authority has the power to review and decide appeals arising from cases within a specified court, region, or jurisdiction.
  • E. crossedWith
    Indicates that one entity has moved from one side of another entity or boundary to the opposite side, typically by passing over or through it.
  • F. None of above. chosen

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_69b3454965f881908c41190bb22f0e4b completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b351c68a588190ba14a298afacb1dc completed March 12, 2026, 11:52 p.m.
PD Predicate disambiguation batch_69b34f51ed7c8190b7bf5f44b56b730d completed March 12, 2026, 11:42 p.m.
PDg Predicate description generation batch_69b34ff654308190b9717526120d80d3 completed March 12, 2026, 11:44 p.m.
Created at: March 12, 2026, 11:16 p.m.