Triple
T28836356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daytime Protocol |
E728193
|
entity |
| Predicate | supportsMultipleResponsesPerConnection |
P203799
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Daytime Protocol, supportsMultipleResponsesPerConnection, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMultipleResponsesPerConnection Context triple: [Daytime Protocol, supportsMultipleResponsesPerConnection, false]
-
A.
supportsMultipleStreams
Indicates that the subject is capable of handling or maintaining more than one data or communication stream at the same time.
-
B.
supportsMultipleLayersPerRequest
Indicates that a single request can handle or process multiple layers at the same time.
-
C.
supportsMultiSocketConfiguration
Indicates that the subject is capable of operating correctly with multiple sockets or socket connections configured simultaneously.
-
D.
supportsMultipleRanges
Indicates that an entity can handle, accept, or operate over more than one distinct range of values or intervals.
-
E.
supportsMultipleObjects
Indicates that the relationship or action can simultaneously involve or apply to more than one object at the same time.
- F. None of above. chosen
Provenance (4 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a0207a1272c81909dcdb6e3307702f5 |
completed | May 11, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a0205fa1e608190829fd2baa0434fff |
completed | May 11, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_6a0207a073508190adf36e94ab2380ad |
completed | May 11, 2026, 4:45 p.m. |
Created at: April 28, 2026, 6:39 a.m.