Triple

T14531235
Position Surface form Disambiguated ID Type / Status
Subject Yahoo! Messenger E340918 entity
Predicate competitor P1375 FINISHED
Object AOL Instant Messenger E10976 NE 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: AOL Instant Messenger | Statement: [Yahoo! Messenger, competitor, AOL Instant Messenger]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: AOL Instant Messenger
Context triple: [Yahoo! Messenger, competitor, AOL Instant Messenger]
  • A. AOL Instant Messenger chosen
    AOL Instant Messenger was a pioneering late-1990s and early-2000s instant messaging service that popularized online chat and status-based communication for mainstream internet users.
  • B. Yahoo! Messenger
    Yahoo! Messenger was a popular instant messaging client and service from Yahoo that enabled real-time text, voice, and video communication, widely used in the late 1990s and 2000s.
  • C. ICQ
    ICQ is one of the earliest popular internet instant messaging services, widely used in the late 1990s and early 2000s.
  • D. MSN Messenger
    MSN Messenger was a widely used instant messaging client developed by Microsoft that enabled real-time text, voice, and video communication over the internet.
  • E. Adium
    Adium is a free, open-source instant messaging client for macOS that supports multiple chat protocols through a unified interface.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d822dac79c8190a84a073f3cbaced5 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dea052d01c81909c8592c351be6f35 completed April 14, 2026, 8:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd7a56872c8190a6d2421cb81aeeb1 completed May 8, 2026, 5:53 a.m.
Created at: April 10, 2026, 1:22 a.m.