Triple
T8697104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7540 |
E206428
|
entity |
| Predicate | introducesFeature |
P513
|
FINISHED |
| Object | Stream multiplexing |
—
|
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: Stream multiplexing | Statement: [RFC 7540, introducesFeature, Stream multiplexing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesFeature Context triple: [RFC 7540, introducesFeature, Stream multiplexing]
-
A.
introducedFeatureCategory
Indicates that an entity caused a particular feature category to be created, presented, or made available for the first time.
-
B.
introducedFeatureFamily
Indicates that an entity (such as a product or version) was responsible for first introducing a particular feature family.
-
C.
serviceIntroduced
Indicates that a particular service has been launched, made available, or brought into operation at a certain time or context.
-
D.
introduced
chosen
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
E.
introducedTeamFeature
Indicates that an entity launched or made available a new feature specifically designed for teams.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc582b04688190a439135b08e20451 |
completed | March 31, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:34 p.m.