Triple
T27833831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nova-novncproxy |
E703173
|
entity |
| Predicate | proxiesProtocol |
P61520
|
FINISHED |
| Object | VNC |
—
|
LITERAL 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 | Statement: [nova-novncproxy, proxiesProtocol, VNC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proxiesProtocol Context triple: [nova-novncproxy, proxiesProtocol, VNC]
-
A.
targetsProtocol
Indicates that one entity is designed to interact with, affect, or be applied to a specific protocol.
-
B.
targetProtocol
Indicates the communication protocol that an action, message, or connection is intended to use or be directed toward.
-
C.
transportProtocol
Indicates the communication protocol used to transport data between entities in a networked interaction.
-
D.
encapsulatesProtocol
chosen
Indicates that one entity implements and contains the functionality of a specific communication or interaction protocol on behalf of another entity.
-
E.
optionalProtocolMonitored
Indicates that monitoring of the specified protocol is supported but not required or always enabled.
- F. None of above.
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_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6389e32ec8190aad8e24090ec980a |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:58 p.m.