Triple
T4945241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Anderson |
E111033
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | social networking pioneer |
C17
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: social networking pioneer Context triple: [Tom Anderson, instanceOf, social networking pioneer]
-
A.
microblogging service operator
A microblogging service operator is an entity responsible for running, maintaining, and moderating a platform that enables users to post, share, and interact with short-form content in real time.
-
B.
information technology pioneer
chosen
An information technology pioneer is an individual who significantly advances the development, application, or understanding of computing and digital technologies, often introducing groundbreaking concepts, systems, or practices that shape the evolution of the IT field.
-
C.
social media personality
A social media personality is an individual who builds and maintains a recognizable public persona and audience primarily through content creation and interaction on digital platforms.
-
D.
collective of internet users
A collective of internet users is a loosely organized group of individuals connected through online platforms who share, create, and interact around common interests, goals, or activities.
-
E.
collaborative online platform
A collaborative online platform is a digital environment that enables multiple users to work together in real time or asynchronously by sharing information, coordinating tasks, and communicating through integrated tools and services.
- F. None of above.
Provenance (1 batch)
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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:31 p.m.