Triple
T8289150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virtual Network Computing |
E193851
|
entity |
| Predicate | component |
P35
|
FINISHED |
| Object | VNC viewer |
E721427
|
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: VNC viewer | Statement: [Virtual Network Computing, component, VNC viewer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VNC viewer Context triple: [Virtual Network Computing, component, VNC viewer]
-
A.
VNC
chosen
VNC (Virtual Network Computing) is a graphical desktop-sharing system that allows users to remotely control another computer’s desktop over a network.
-
B.
x11vnc
x11vnc is a VNC server for Unix-like systems that allows remote access to an existing X11 desktop session.
-
C.
TeamViewer
TeamViewer is a German software company best known for its remote access and remote control solutions that allow users to connect to and manage devices over the internet.
-
D.
Remote Desktop Web Client
Remote Desktop Web Client is a browser-based interface that lets users access and control remote Windows desktops and applications without installing a dedicated client.
-
E.
Remote Desktop Protocol
Remote Desktop Protocol is a Microsoft-developed network communication standard that enables users to remotely access and control Windows-based computers with a graphical interface over a network.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7c98e15c8190ac2a0b2a5ff834c9 |
completed | March 31, 2026, 7:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd952399dc8190914951d4e9e36c38 |
completed | April 1, 2026, 9:58 p.m. |
Created at: March 30, 2026, 5:52 p.m.