Triple

T1257853
Position Surface form Disambiguated ID Type / Status
Subject ICQ E12432 entity
Predicate supportsProtocol P203 FINISHED
Object ICQ protocol E12432 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: ICQ protocol | Statement: [ICQ, supportsProtocol, ICQ protocol]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ICQ protocol
Context triple: [ICQ, supportsProtocol, ICQ protocol]
  • A. ICQ chosen
    ICQ is one of the earliest popular internet instant messaging services, widely used in the late 1990s and early 2000s.
  • B. AOL Instant Messenger
    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.
  • C. XMPP
    XMPP (Extensible Messaging and Presence Protocol) is an open, XML-based communication protocol primarily used for instant messaging, presence information, and real-time data exchange over the internet.
  • D. IRC
    IRC is the commonly used abbreviation for the Internal Revenue Code, the comprehensive body of federal tax laws in the United States.
  • E. IRC
    IRC (Internet Relay Chat) is a long-standing, text-based communication protocol that enables real-time group and private messaging over the internet via channels and servers.
  • 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_69a4933352e08190ac617291985e76c0 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4bfaa2b508190a3f61c67b3fa3ad4 completed March 1, 2026, 10:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac93cdba808190b7d164bb98efe3dc completed March 7, 2026, 9:08 p.m.
Created at: March 1, 2026, 7:50 p.m.