Triple
T6360549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirabilis |
E143096
|
entity |
| Predicate | product |
P490
|
FINISHED |
| Object | ICQ |
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 | Statement: [Mirabilis, product, ICQ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ICQ Context triple: [Mirabilis, product, ICQ]
-
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.
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.
-
D.
BlackBerry Messenger
BlackBerry Messenger was a proprietary instant messaging service for BlackBerry devices that became widely popular for its secure, real-time chat and push notifications before the rise of modern smartphone messaging apps.
-
E.
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.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067f8758081909c5ce40abf57dd2c |
completed | March 22, 2026, 10:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c63869ef148190816b152f2724de49 |
completed | March 27, 2026, 7:57 a.m. |
Created at: March 22, 2026, 4:32 p.m.