Triple
T161269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web 2.0 |
E3289
|
entity |
| Predicate | hasExample |
P1259
|
FINISHED |
| Object |
E1582
|
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: Facebook | Statement: [Web 2.0, hasExample, Facebook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Facebook Context triple: [Web 2.0, hasExample, Facebook]
-
A.
Facebook
chosen
Facebook is a major global social networking platform that allows users to connect, share content, and communicate online.
-
B.
Instagram
Instagram is a popular photo and video sharing social media platform known for its visual content, stories, and influencer culture.
-
C.
Snap Inc.
Snap Inc. is an American technology and social media company best known for developing the multimedia messaging app Snapchat and related camera and augmented reality products.
-
D.
Google
Google is a multinational technology company best known for its search engine and wide range of internet-related products and services, including Android, YouTube, and cloud computing.
-
E.
Tumblr
Tumblr is a microblogging and social networking platform known for its highly customizable blogs, fandom communities, and viral multimedia content.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a25856d934819095460b2ea566eb6b |
completed | Feb. 28, 2026, 2:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a2d7343fc08190810b11d205e41d9a |
completed | Feb. 28, 2026, 11:53 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.