Triple
T33029332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Direct Client-to-Client |
E845120
|
entity |
| Predicate | dataChannel |
P92334
|
FINISHED |
| Object | separate direct TCP connection |
—
|
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: separate direct TCP connection | Statement: [Direct Client-to-Client, dataChannel, separate direct TCP connection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataChannel Context triple: [Direct Client-to-Client, dataChannel, separate direct TCP connection]
-
A.
definesDataChannel
chosen
Indicates that one entity specifies or establishes a data transmission channel to be used for communication or data exchange with another entity.
-
B.
dataChannelUsage
Indicates how a data channel is utilized or engaged in communication or data transfer between entities.
-
C.
dataCollectionChannel
Indicates the medium or method through which data is gathered or received from a source.
-
D.
virtualChannel
Indicates that one entity is linked to another through a non-physical, software-defined communication channel used for transmitting data or signals.
-
E.
canChannel
Indicates that one entity is able to direct, transmit, or route something (such as information, energy, or resources) through another entity or medium.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:24 a.m.