Triple

T13894882
Position Surface form Disambiguated ID Type / Status
Subject Yahoo homepage E334061 entity
Predicate supportsPersonalization P111922 FINISHED
Object true 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: true | Statement: [Yahoo homepage, supportsPersonalization, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsPersonalization
Context triple: [Yahoo homepage, supportsPersonalization, true]
  • A. supportsPersonalRequests
    Indicates that an entity is willing or able to assist another entity with non-professional, individual, or private requests.
  • B. hasPersonalThemes
    Indicates that something (such as a work, message, or expression) involves themes that are personal, intimate, or directly related to an individual’s own experiences or inner life.
  • C. supportsIdentity
    Indicates that one entity upholds, validates, or reinforces the identity, self-concept, or role of another entity.
  • D. supportsMood
    Indicates that one entity helps maintain, enhance, or positively influence the emotional state or mood of another entity.
  • E. supportsThemeOf
    Indicates that one entity reinforces, aligns with, or contributes to the central theme expressed by another entity.
  • 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_69d81c5dd2d48190b7a5fc1e009de936 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de23a741908190bdf46d76c5f1411a completed April 14, 2026, 11:23 a.m.
PD Predicate disambiguation batch_69dd464b1ab48190ae50bfc902bf6ef7 completed April 13, 2026, 7:38 p.m.
PDg Predicate description generation batch_69de01ed2098819088ec45069f6f2609 completed April 14, 2026, 8:59 a.m.
Created at: April 9, 2026, 10:15 p.m.