Triple

T20622189
Position Surface form Disambiguated ID Type / Status
Subject SRK 6063 E506726 entity
Predicate sideAContains P34740 FINISHED
Object Don’t Come Close NE NERFINISHED

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: Don’t Come Close | Statement: [SRK 6063, sideAContains, Don’t Come Close]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Don’t Come Close
Context triple: [SRK 6063, sideAContains, Don’t Come Close]
  • A. Don’t Come Close chosen
    "Don’t Come Close" is a song by the American punk rock band Ramones, featured on their 1978 album "Road to Ruin."
  • B. So Close
    So Close is a popular song by South Korean singer JR, recognized as one of his standout solo releases.
  • C. So Close
    "So Close" is a popular electronic dance track by German DJ and producer Felix Jaehn, known for its catchy melody and radio-friendly sound.
  • D. Come Close
    "Come Close" is a soulful hip-hop single by Common, produced by The Neptunes and known for its intimate, romantic lyrics.
  • E. Too Close
    "Too Close" is a 1998 R&B hit single by American group Next, best known for its sensual lyrics and chart-topping success.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4bc90988190ac360aaf645efc1d completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6abe25c208190af057bcd1aa6219d completed April 20, 2026, 10:42 p.m.
Created at: April 16, 2026, 11:42 a.m.