Triple
T27755848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .NET Remoting |
E701330
|
entity |
| Predicate | supportsChannelType |
P116567
|
FINISHED |
| Object | TCP channel |
—
|
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: TCP channel | Statement: [.NET Remoting, supportsChannelType, TCP channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsChannelType Context triple: [.NET Remoting, supportsChannelType, TCP channel]
-
A.
supportsChannels
Indicates that one entity is capable of handling, providing, or being compatible with one or more specified channels for communication, distribution, or operation.
-
B.
includesChannelType
chosen
Indicates that one entity encompasses or supports a specified type of communication or distribution channel as part of its structure or functionality.
-
C.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
D.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
-
E.
supportsGroupType
Indicates that one entity is compatible with or able to support a particular category or type of group.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_6a0004582bb08190b8d0b88251e8d333 |
completed | May 10, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a0003e3e5588190933beea5fb28f150 |
completed | May 10, 2026, 4:04 a.m. |
Created at: April 27, 2026, 4:23 p.m.